> I wold like to setup server side quorum by using the following setup:
> - 2x storage nodes (s-node-1, s-node-2)
> - 1x arbiter node (s-node-3)
> So the trusted storage pool has three peers.
>
> This is my volume info:
> Volume Name: wp-vol-0
> Type: Replicate
> Volume ID: 8808ee87-b201-474f-83ae-6f08eb259b43
> Status: Started
> Number of Bricks: 1 x 2 = 2
> Transport-type: tcp
> Bricks:
> Brick1: s-node-1:/gluster/gvol0/brick0/brick
> Brick2: s-node-2:/gluster/gvol0/brick0/brick
>
> I would like to setup the server side quorum so that any two nodes would
> have quorum.
> s-node-1, s-node-2 = quorum
> s-node-1, s-node-3 = quorum
> s-node-2, s-node-3 = quorum
> According to the Gluster guys at FOSDEM this should be possible.
>
> I have been fiddling with the quorum options, but have not been able to
> achieve the desired setup.
> Theoretically I would do:
> # gluster volume set wp-vol-0 cluster.server-quorum-type server
> # gluster volume set wp-vol-0 cluster.server-quorum-ratio 60
>
> But the cluster.server-quorum-ratio option produces an error:
> volume set: failed: Not a valid option for single volume
>
> How would I achieve the desired setup?
Somewhat counter-intuitively, server-quorum-type is a *volume* option
but server-quorum-ratio is a *cluster wide* option. Therefore, instead
of specifying a volume name on that command, use this:
# gluster volume set all cluster.server-quorum-ratio 60
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
