Bug 818136
| Summary: | [RFE] Geo-replication Fail-over | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Divya <divya> |
| Component: | doc-User_Guide | Assignee: | Divya <divya> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | amainkar |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.0 | CC: | asriram, mhideo, rwheeler, sdharane, storage-doc |
| Target Milestone: | Release Candidate | Keywords: | FutureFeature |
| Target Release: | RHGS 2.0.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-04-10 07:17:37 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: | |||
|
Description
Divya
2012-05-02 10:22:16 UTC
*** Bug 821869 has been marked as a duplicate of this bug. *** As of I have understood about the f/o and f/b feature is , we are not giving out the detailed steps involved in the Fail-over and Fail-back to the user , but rather we just mention, what this feature is capable of and how should a customer approach, to use this feature. For that , I think this is sufficient in the documentation.
Red Hat Storage 2.0 supports Geo-Replication failover and failback. If the master goes down, you can trigger a failover procedure so that the slave can be replaced as the master. During this time, all I/O operations including writes and reads are done on the slave (now acting as master). When the original master (OM) is back online, you can trigger a failback procedure on the original slave (OS) so that it syncs the delta back to the master.
And then in the note section, we can mention,
Note : "Implementation of f/o and f/b for production mandates a Red Hat Professional Services engagement. Please contact your Red Hat representative for more information." Something like that.
But Documentation already has the detailed steps to execute. I feel we should remove that.
I have added a Warning on engaging Red Hat Professional Services and retained instructions on triggering Failover and Failback based on Sayan's suggestion. The updated documentation is available at: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Storage/2.0/html/Administration_Guide/ch11s05.html |