[Bugs] [Bug 1371543] Add cache invalidation stat in profile info

bugzilla at redhat.com bugzilla at redhat.com
Thu Sep 1 03:18:46 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1371543



--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15193 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com) 
------
commit ee0d8ca53f685f8f27c93b3d7c808f2a78c1ae43
Author: Poornima G <pgurusid at redhat.com>
Date:   Wed Aug 17 20:19:59 2016 +0530

    io-stats: Add stats for upcall notifications

    With this patch, there will be additional entries seen in
    the profile info:

    UPCALL : Total number of upcall events that were sent from
             the brick(in brick profile), and number of upcall
             notifications recieved by client(in client profile)

    Cache invalidation events:
    -------------------------
    CI_IATT : Number of upcalls that were cache invalidation and
             had one of the IATT_UPDATE_FLAGS set. This indicates
             that one of the iatt value was changed.

    CI_XATTR : Number of upcalls that were cache invalidation, and
             had one of the UP_XATTR or UP_XATTR_RM set. This indicates
             that an xattr was updated or deleted.

    CI_RENAME : Number of upcalls that were cache invalidation,
             resulted by the renaming of a file or directory

    CI_UNLINK : Number of upcalls that were cache invalidation,
             resulted by the unlink of a file.

    CI_FORGET : Number of upcalls that were cache invalidation,
             resulted by the forget of inode on the server side.

    Lease events:
    ------------
    LEASE_RECALL : Number of lease recalls sent by the brick (in
             brick profile), and number of lease recalls recieved
             by client(in client profile)

    Note that the sum of CI_IATT, CI_XATTR, CI_RENAME, CI_UNLINK,
    CI_FORGET, LEASE_RECALL may not be equal to UPCALL. This is
    because, each cache invalidation can carry multiple flags.
    Eg:
    - Every CI_XATTR will have CI_IATT
    - Every CI_UNLINK will also increment CI_IATT as link count is an
    iatt attribute.

    Also UP_PARENT_DENTRY_FLAGS is currently not accounted for,
    as CI_RENAME and CI_UNLINK will always have the flag
    UP_PARENT_DENTRY_FLAGS

    Change-Id: Ieb8cd21dde2c4c7618f12d025a5e5156f9cc0fe9
    BUG: 1371543
    Signed-off-by: Poornima G <pgurusid at redhat.com>
    Reviewed-on: http://review.gluster.org/15193
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list