[Bugs] [Bug 1477404] eager-lock should be off for cassandra to work at the moment

bugzilla at redhat.com bugzilla at redhat.com
Wed Aug 2 04:45:57 UTC 2017


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



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17954 committed in master by Krutika
Dhananjay (kdhananj at redhat.com) 
------
commit 0cc24da2fd79dd8680b771475d2192db0b63e7de
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Wed Aug 2 07:22:13 2017 +0530

    extras: Turn eager-lock off for gluster-block

    With the current implementation of eager-lock FINODELK is taking so much
    time that cassandra workload times out and errors out. AFR eager-locking
    needs to be changed similar to EC eager-locking to make things work
    as expected. In the interim, it is better to turn it off

    This is how the profile looks if eager-lock is turned on:
          0.35     628.26 us      64.00 us  129882.00 us          42278   
FXATTROP
         17.45   16500.54 us     212.00 us  375829.00 us          79568      
WRITE
         81.76  209862.12 us      15.00 us 1992486.00 us          29318   
FINODELK

    This is how profile looks if eager-lock is turned off:
          1.87     283.71 us      65.00 us  298970.00 us          68346   
FXATTROP
          6.33     199.04 us      13.00 us  373428.00 us         330524   
FINODELK
         10.37    3151.47 us      53.00 us 1528484.00 us          34172      
FSYNC
         81.31    5110.45 us     270.00 us 1519722.00 us         165244      
WRITE

    BUG: 1477404
    Change-Id: I98026b1ecf30002ddac01be76f375c2e8c0b7838
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: https://review.gluster.org/17954
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Tested-by: Krutika Dhananjay <kdhananj at redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj 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