Bug 1095585
Summary: | Two instances each, of brick processes, glusterfs-nfs and quotad seen after glusterd restart | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Kaushal <kaushal> | |
Component: | glusterd | Assignee: | Kaushal <kaushal> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | mainline | CC: | bugs, dpati, esammons, gluster-bugs, kaushal, knarra, nsathyan, ssamanta, ssampat | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.6.0beta1 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1092429 | |||
: | 1105188 (view as bug list) | Environment: | ||
Last Closed: | 2014-11-11 08:32:00 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: | ||||
Bug Blocks: | 1092429, 1105188 |
Description
Kaushal
2014-05-08 05:16:01 UTC
REVIEW: http://review.gluster.org/7703 (glusterd: On gaining spawn_daemons using a synctask) posted (#1) for review on master by Kaushal M (kaushal) REVIEW: http://review.gluster.org/7703 (glusterd: On gaining quorum spawn_daemons in new thread) posted (#2) for review on master by Kaushal M (kaushal) REVIEW: http://review.gluster.org/7703 (glusterd: On gaining quorum spawn_daemons in new thread) posted (#3) for review on master by Kaushal M (kaushal) REVIEW: http://review.gluster.org/7703 (glusterd: On gaining quorum spawn_daemons in new thread) posted (#4) for review on master by Kaushal M (kaushal) COMMIT: http://review.gluster.org/7703 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 4f905163211f8d439c6e102d3ffd1bffb34f5c26 Author: Kaushal M <kaushal> Date: Wed May 7 18:17:11 2014 +0530 glusterd: On gaining quorum spawn_daemons in new thread During startup, if a glusterd has peers, it waits till quorum is obtained to spawn bricks and other services. If peers are not present, the daemons are started during glusterd' startup itself. The spawning of daemons as a quorum action was done without using a seperate thread, unlike the spawn on startup. Since, quotad was launched using the blocking runner_run api, this leads to the thread being blocked. The calling thread is almost always the epoll thread and this leads to a deadlock. The runner_run call blocks the epoll thread waiting for quotad to start, as a result glusterd cannot serve any requests. But the startup of quotad is blocked as it cannot fetch the volfile from glusterd. The fix for this is to launch the spawn daemons task in a seperate thread. This will free up the epoll thread and prevents the above deadlock from happening. Change-Id: Ife47b3591223cdfdfb2b4ea8dcd73e63f18e8749 BUG: 1095585 Signed-off-by: Kaushal M <kaushal> Reviewed-on: http://review.gluster.org/7703 Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Gluster Build System <jenkins.com> Tested-by: Krishnan Parthasarathi <kparthas> 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.0beta1 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/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/ 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 |