Bug 1158067
| Summary: | Gluster volume monitor hangs glusterfsd process | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Tom Young <tom.young> | ||||
| Component: | glusterd | Assignee: | bugs <bugs> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.6.0 | CC: | bugs, kwade, ndevos, smohan, tom.young | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-08-01 04:42:28 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: | |||||||
| Attachments: |
|
||||||
Tom, Could you attach the glusterd logs, from the nodes participating in the cluster, to the bug? I have also modified the product to GlusterFS which is the community version. Hope that's accurate. This sounds fairly serious. Should it be a 3.6.0 blocker, or could the fix for this wait until 3.6.1? The fix can certainly wait, we have moved to 3.6.1 and I have not seen the problem return. glusterfs-3.6.1-1.el6.x86_64 Cool. Sounds like it may already be fixed then. :D KP, could you mark this bug as a duplicate of the one that added improvements to the locking in Glusterd? Thanks! This is not a security bug, not going to fix this in 3.6.x because of http://www.gluster.org/pipermail/gluster-users/2016-July/027682.html If the issue persists in the latest releases, please feel free to clone them The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Created attachment 951404 [details] status check used to monitor the bricks for GFS Description of problem: Using a gluster volume monitor to check on the status of the bricks for my volumes can cause the glusterfsd process to hang. Version-Release number of selected component (if applicable): glusterfs-3.6.0-0.5.beta3 How reproducible: When I execute the script to check the volume status from each node, I can hang the glusterfsd process each time. Steps to Reproduce: 1.Exectute the monitoring script from each node, at the same time. 2. 3. Actual results: Another transaction is in progress. Please try again after sometime. Expected results: I should get the status of the volumes, if they're online, or offline. Additional info: