REVIEW: https://review.gluster.org/21739 (geo-rep: Make slave volume read-only (by default)) posted (#1) for review on master by Harpreet Kaur Lalwani
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)
This can be easily done during create command.
Just have to add the below command in hookscript
gluster vol set <slave_vol> features.read-only on
For root geo-rep:
$SRC//extras/hook-scripts/S56glusterd-geo-rep-create-post.sh for root geo-rep
For non-root geo-rep:
REVIEW: https://review.gluster.org/21739 (geo-rep: Make slave volume read-only (by default)) posted (#8) for review on master by Kotresh HR
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report.
glusterfs-6.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.