Bug 1449684 - rchecksum is not shown in profile info
Summary: rchecksum is not shown in profile info
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: core
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.3.0
Assignee: Ravishankar N
QA Contact: Vinayak Papnoi
URL:
Whiteboard:
Depends On:
Blocks: 1417151
TreeView+ depends on / blocked
 
Reported: 2017-05-10 12:47 UTC by Ravishankar N
Modified: 2017-09-21 04:41 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.8.4-26
Doc Type: If docs needed, set a value
Doc Text:
Previously, certain FOPs (fentrylk, rchecksum, seek, lease, getactivelk, setactivelk, compound fops) were missing from volume profile info output. These are now captured as expected.
Clone Of:
Environment:
Last Closed: 2017-09-21 04:41:45 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2774 0 normal SHIPPED_LIVE glusterfs bug fix and enhancement update 2017-09-21 08:16:29 UTC

Description Ravishankar N 2017-05-10 12:47:49 UTC 
Description of problem:
I am facing a lot of customer issues where I see high cpu usage but I am not able to ascertain from the profile info if it is due to the rchecksum which self-heal does. The fix is already available upstream https://review.gluster.org/16490. We need this downstream code also.
Comment 2 Ravishankar N 2017-05-10 12:53:10 UTC 
Patch: https://code.engineering.redhat.com/gerrit/#/c/105802/
Comment 6 Vinayak Papnoi 2017-06-15 11:49:42 UTC 
gluster build: 3.8.4-26

Did the following to get the profile info:
#create vol-start-mount
#Create a file using "touch f1"
#kill 1 brick using "kill -9 <pid>"
#Write data to the file using "dd if=/dev/zero of=f1 bs=1M count=2"
#Start the volume using volume force
#Check the volume profile info 

Outcome: out of the FOP's mentioned in the doc, only rchecksum was displayed.

      0.00       0.00 us       0.00 us       0.00 us              4     RELEASE
      0.00       0.00 us       0.00 us       0.00 us             10  RELEASEDIR
      0.07       5.33 us       4.00 us       9.00 us              6     OPENDIR
      0.12      58.00 us      58.00 us      58.00 us              1       FLUSH
      0.57     279.00 us     279.00 us     279.00 us              1 REMOVEXATTR
      0.82     397.00 us     397.00 us     397.00 us              1    TRUNCATE
      1.13     275.00 us     231.00 us     319.00 us              2       FSTAT
      1.50     121.33 us      58.00 us     245.00 us              6    FINODELK
      2.03     330.00 us     241.00 us     503.00 us              3        OPEN
      4.22     410.40 us     228.00 us     844.00 us              5     XATTROP
      4.56     201.91 us      47.00 us     868.00 us             11    GETXATTR
      5.64     171.56 us      91.00 us    1042.00 us             16        READ
      6.09     296.60 us     115.00 us     517.00 us             10    FXATTROP
      7.82      88.47 us      43.00 us     347.00 us             43     INODELK
      8.25     267.67 us      50.00 us    1282.00 us             15      LOOKUP
     10.49     425.58 us     347.00 us     618.00 us             12     READDIR
     13.32     405.12 us     307.00 us     637.00 us             16       WRITE
     33.37    1015.06 us     985.00 us    1130.00 us             16   RCHECKSUM
 
    Duration: 269 seconds
   Data Read: 2097152 bytes
Data Written: 2097152 bytes
Comment 7 Vinayak Papnoi 2017-07-28 10:42:47 UTC 
Build: 3.8.4-35

Followed the steps mentioned above. As per the result the RCHECKSUM FOP is mentioned in volume profile info.

Hence, moving this bug to VERIFIED.
Comment 9 errata-xmlrpc 2017-09-21 04:41:45 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2774
Note You need to log in before you can comment on or make changes to this bug.