Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1145095

Summary: [SNAPSHOT]: snapshot create fails with error in log "Failed to open directory <xyz>, due to many open files"
Product: [Community] GlusterFS Reporter: Sachin Pandit <spandit>
Component: glusterdAssignee: Sachin Pandit <spandit>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: bugs, gluster-bugs, nsathyan, rhinduja, ssamanta, vmallika
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: SNAPSHOT
Fixed In Version: glusterfs-3.6.0beta2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1136352 Environment:
Last Closed: 2014-11-11 08:39:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1134316, 1136352    
Bug Blocks:    

Comment 1 Anand Avati 2014-09-22 11:34:25 UTC
REVIEW: http://review.gluster.org/8807 (glusterd: Set the rlimit for Open FDs to higher value) posted (#1) for review on release-3.6 by Sachin Pandit (spandit)

Comment 2 Anand Avati 2014-09-22 11:52:13 UTC
REVIEW: http://review.gluster.org/8807 (glusterd: Set the rlimit for Open FDs to higher value.) posted (#2) for review on release-3.6 by Sachin Pandit (spandit)

Comment 3 Anand Avati 2014-09-23 10:14:57 UTC
COMMIT: http://review.gluster.org/8807 committed in release-3.6 by Vijay Bellur (vbellur) 
------
commit 07235e99003693687e349f74d5627bd8c53ff1e0
Author: Vijaikumar M <vmallika>
Date:   Tue Sep 2 17:43:43 2014 +0530

    glusterd: Set the rlimit for Open FDs to higher value.
    
    Default 'open FD limit' is 1024. As the number of volumes/bricks
    increases, brick-to-glusterd socket FDs also increases in glusterd and
    runs out of the limit.
    
    Solution is to set the 'Open FD' limit to higher value in glusterd
    
    Change-Id: Iaa60b2155df2fa5a0759e054bdebffbc09f63ec1
    BUG: 1145095
    Signed-off-by: Vijaikumar M <vmallika>
    Reviewed-on: http://review.gluster.org/8578
    Reviewed-by: Rajesh Joseph <rjoseph>
    Reviewed-by: Atin Mukherjee <amukherj>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Krishnan Parthasarathi <kparthas>
    Signed-off-by: Sachin Pandit <spandit>
    Reviewed-on: http://review.gluster.org/8807

Comment 4 Niels de Vos 2014-09-25 08:27:48 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta2 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018883.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 5 Niels de Vos 2014-11-11 08:39:59 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users