Bug 1230102
| Summary: | Document that client-quorum is enabled by default in replica 3 volume | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> |
| Component: | doc-Administration_Guide | Assignee: | Divya <divya> |
| doc-Administration_Guide sub component: | Default | QA Contact: | SATHEESARAN <sasundar> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | high | ||
| Priority: | unspecified | CC: | asriram, asrivast, divya, mhideo, nlevinki, rhs-bugs, rwheeler, storage-doc |
| Version: | rhgs-3.1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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: | 1202842 | ||
|
Description
SATHEESARAN
2015-06-10 09:07:58 UTC
Added information that client-side quorum is enabled by default in the following sections of the doc: 6.4.2. Creating Three-way Replicated Volumes - http://jenkinscat.gsslab.pnq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.1-Administration_Guide%20%28html-single%29/lastStableBuild/artifact/tmp/en-US/html-single/index.html#Creating_Three-way_Replicated_Volumes 6.5.2. Creating Three-way Distributed Replicated Volumes - http://jenkinscat.gsslab.pnq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.1-Administration_Guide%20%28html-single%29/lastStableBuild/artifact/tmp/en-US/html-single/index.html#Creating_Three-way_Distributed_Replicated_Volumes Good that all places in admin guide which mentions about creating replica 3 (1X3) or distributed-replica with replica count 3 ( Nx3 ), has this note about the default behaviour of client-side quorum Marking this bug as VERIFIED with the jenkinscat link available in comment1 |