Bug 1662889 - Geo-rep doc update for default setting of slave in read-only mode.
Summary: Geo-rep doc update for default setting of slave in read-only mode.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: Documentation
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHGS 3.4.z Batch Update 3
Assignee: Chandrakanth Pai
QA Contact: Rochelle
URL:
Whiteboard:
Depends On:
Blocks: 1660873
TreeView+ depends on / blocked
 
Reported: 2019-01-02 10:19 UTC by Harpreet Kaur Lalwani
Modified: 2019-02-08 13:09 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-08 13:09:48 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Harpreet Kaur Lalwani 2019-01-02 10:19:07 UTC
Document URL: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/html-single/administration_guide/#idm140101750753216

Section Number and Name: 10.3.4 and Setting Up your Environment

Describe the issue: Geo-rep Doc includes an additional command to set slave vol 
in read-only mode to avoid being written by clients other than geo-replication.
We are making slave volume read-only by default. So we do not need this additional setting during geo-rep setup. But in the case of a failover-failback situation, the original master is made read-only by default
as the session is from the original slave to the original master.

Suggestions for improvement: The section 10.3.4 needs to be updated as we do not need the additional setting of changing slave to read-only mode.
We also need to update section 10.7.1 Failover: Promoting a Slave to Master and section 10.7.2 Failback: Resuming Master and Slave back to their Original State, where we have to manually revert this default setting such that the master does not gets this read-only setting.
 

Additional information:


Note You need to log in before you can comment on or make changes to this bug.