Bug 1226146 - BitRot :- bitd is not signing Objects if more than 3 bricks are present on same node
Summary: BitRot :- bitd is not signing Objects if more than 3 bricks are present on sa...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: bitrot
Version: 3.7.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Venky Shankar
QA Contact: RajeshReddy
bugs@gluster.org
URL:
Whiteboard:
Depends On:
Blocks: qe_tracker_everglades glusterfs-3.7.1 1221560 1221605 1224182 1224193
TreeView+ depends on / blocked
 
Reported: 2015-05-29 05:41 UTC by Venky Shankar
Modified: 2015-12-01 16:45 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.7.1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1207134
Environment:
Last Closed: 2015-06-02 08:04:11 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2015-05-29 06:07:49 UTC
REVIEW: http://review.gluster.org/10986 (features/bitrot: refactor brick connection logic) posted (#1) for review on release-3.7 by Venky Shankar (vshankar)

Comment 2 Anand Avati 2015-05-31 04:15:13 UTC
COMMIT: http://review.gluster.org/10986 committed in release-3.7 by Venky Shankar (vshankar) 
------
commit 2ef27f82c3705b18e2c3c030b8debcdb7b30e33b
Author: Raghavendra Bhat <raghavendra>
Date:   Wed May 13 14:35:47 2015 +0530

    features/bitrot: refactor brick connection logic
    
        Backport of http://review.gluster.org/10763
    
    Brick connection was bloated (and not implemented efficiently) with
    calls which were not required to be called under lock. This resulted
    in starvation of lock by critical code paths. This eventally did not
    scale when the number of bricks per volume increases (add-brick and
    the likes).
    
    Also, this patch cleans up some of the weird reconnection logic that
    added more to the starvation of resources and cleans up uncontrolled
    growing of log files.
    
    Change-Id: I05e737f2a9742944a4a543327d167de2489236a4
    BUG: 1226146
    Original-Author: Raghavendra Bhat <raghavendra>
    Signed-off-by: Venky Shankar <vshankar>
    Reviewed-on: http://review.gluster.org/10986
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>

Comment 3 Niels de Vos 2015-06-02 08:04:11 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.1, please reopen this bug report.

glusterfs-3.7.1 has been announced on the Gluster Packaging mailinglist [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.packaging/1
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


Note You need to log in before you can comment on or make changes to this bug.