On 08/22/2015 02:30 AM, Pat Riehecky wrote:
At home I've a very small gluster cluster (2 nodes) with a few
volumes. Basically I've set up gluster volumes for "irreplaceable"
content that is replicated to a few systems - for example, photos. But
one system is currently out due to a failed PSU. I'd like to keep the
volume accessible to the rest of my network, but as Read Only. The
cluster.server-quorum-ratio looks to bring the volume off line if the
quorum isn't met. Since nearly all the access to these files is Read
Only anyway I can just defer the writes, is there a tunable that will
automatically put the volume into Read Only when the quorum isn't met
and then bring it back to Read Write automatically when enough bricks
check in?
tldr; cluster.server-quorum-ratio looks to bring volumes off line
when the quorum isn't met, I'd rather go Read Only than off line.
cluster.client-quorum does what you describe, but only for replicate
subvolumes. I suppose manually enabling `features.read-only ` is
something you can use instead.
-Ravi
Pat
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
