Description of problem: ======================= As of now, if we want to make a volume as read-only, we need to specify the volume option and enable it using: gluster volume set <volume_name> features.read-only on In geo-rep, the main idea is to write to the master and that is synced to the slave. Since writes should not happen from the slave, it is good to make the slave as read-only by default to avoid mishaps. In the event of a failover/failback scenario where the slave is made the master and writes need to happen from the slave, this read-only option should simply be disabled (along with enabling the other options which enable the slave volume to sync to the original master)
proposing this for 3.4.3 as the fix helps in avoiding cases from customer(otherwise accidentally then can do destructive action on slave side, and lead to bad experience)
The doc text has been updated. Kindly review the technical accuracy.
Doc text looks good.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0263