Hi,
I'm currently setting up a volume with an arbiter brick.
Are these option values normal in this configuration:
cluster.quorum-type none
cluster.quorum-count(null)
cluster.server-quorum-type off
cluster.server-quorum-ratio 0
Hi,
I have noticed that when using a distribute volume, if a brick is not
accessible, volume is still accessible in read-write mode, but some files can't
be created (depending on filename).
Is it possible to force a distribute volume to be put in read-only mode during
a brick failure, to avoid
Hi,
Maybe I misunderstood, but, sure, you will have failover with CTDB + glusterfs.
Glusterfs allows you to have your shares replicated on several nodes, and CTDB
manages VIP.
If one node goes down, its VIP goes to another node, and shares are still
accessible thanks to glusterfs.
But, as CIFS