Re: Client vs Server Quorum

Lindsay Mathieson <lindsay.mathieson@xxxxxxxxx> · Sun, 11 Oct 2015 17:59:56 +1000

Many thanks for the detailed reply Ravishankar

On 11 October 2015 at 16:27, Ravishankar N <ravishankar@xxxxxxxxxx> wrote:
Question:

                  - Which is better, server or client quorums?

    You can still end up in  split-brain of the files stored in the
    volume  if sever quorum is enabled. Sever quorum is more useful to
    avoid conflicts in volume configuration since it also disallows
    volume set commands, peer probe etc when not in quorum. Client
    quorum is better if you want to avoid split-brains of files present
    in the volume.

                  - Can you safely enable both? recommended?

    IMHO, client-quorum is enough. In case of dist-rep volumes, it acts
    on only those replica sets where quorum is not met making only that
    replica pair EROFS. Server quorum outright kills the bricks, not
    even allowing read access. But yes, you can enable both.  

I'll think about that, but sounds like just client quorum is sufficient, though with VM hosting you probably don't even want read access.

One thing, just to clarify - client quorum is controlled by the following settings?

- cluster.quorum-type
- cluster.quorum-count

Thanks and Cheers,

-- 
Lindsay

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users