Bug 763825 (GLUSTER-2093)
Summary: | volumes cannot start when one node in a replicated setup is down | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Allen Lu <allen> |
Component: | nfs | Assignee: | Shehjar Tikoo <shehjart> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.1.0 | CC: | anush, gluster-bugs, vijay |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | RTP | Mount Type: | nfs |
Documentation: | DNR | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Allen Lu
2010-11-11 19:58:11 UTC
What gluster commands did you use? I cannot understand what you mean by, "if one server is taken down, volumes cannot start." Are you saying that the "gluster volume start <volname>" command does not start nfs server in case a physical server containing a brick is down? PATCH: http://patches.gluster.com/patch/5748 in master (nfs: treat GF_EVENT_CHILD_CONNECTING as subvolume up status) PATCH: http://patches.gluster.com/patch/5782 in master (nfs: Export subvolumes on per-subvolume CHILD-UP) PATCH: http://patches.gluster.com/patch/5786 in master (nfs: Start nfs process even if portmap registration fails) |