Gluster users - Dec 2017 - Syntax for creating arbiter volumes in gluster 4.0

Hi,

The existing syntax in the gluster CLI for creating arbiter volumes is 
`gluster volume create <volname> replica 3 arbiter 1 <list of
bricks>` .
It means (or at least intended to mean) that out of the 3 bricks, 1 
brick is the arbiter.
There has been some feedback while implementing arbiter support in 
glusterd2 for glusterfs-4.0 that we should change this to `replica 2 
arbiter 1` , meaning that there are 2 replica (data) bricks and the 3rd 
one is the arbiter (which only holds meta data).

See [1] for some discussions. What does everyone feel is more user 
friendly and intuitive?

Thanks,
Ravi

[1] https://github.com/gluster/glusterd2/pull/480

On 12/20/2017 05:14 AM, Ravishankar N wrote:
> Hi,
> 
> The existing syntax in the gluster CLI for creating arbiter volumes is
> `gluster volume create <volname> replica 3 arbiter 1 <list of
bricks>` .
> It means (or at least intended to mean) that out of the 3 bricks, 1
> brick is the arbiter.
> There has been some feedback while implementing arbiter support in
> glusterd2 for glusterfs-4.0 that we should change this to `replica 2
> arbiter 1` , meaning that there are 2 replica (data) bricks and the 3rd
> one is the arbiter (which only holds meta data).
I had an additional comment here,

Can we have arbiter 2/3/n? If so the count after the arbiter makes sense
(i.e retaining the '1'), if not then we should drop the number there,
and just call this an arbiter (or some such) volume type. If retained
for future multiple arbiter cases, then it is fine.
> 
> See [1] for some discussions. What does everyone feel is more user
> friendly and intuitive?
> 
> Thanks,
> Ravi
> 
> [1] https://github.com/gluster/glusterd2/pull/480
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users

I definately prefer replica 2 arbiter 1.

It makes more sense and is more accurate, since that scenario has only 
two copies of the actual data.

-wk


On 12/20/2017 2:14 AM, Ravishankar N wrote:
>
> Hi,
>
> The existing syntax in the gluster CLI for creating arbiter volumes is 
> `gluster volume create <volname> replica 3 arbiter 1 <list of
bricks>`
> . It means (or at least intended to mean) that out of the 3 bricks, 1 
> brick is the arbiter.
> There has been some feedback while implementing arbiter support in 
> glusterd2 for glusterfs-4.0 that we should change this to `replica 2 
> arbiter 1` , meaning that there are 2 replica (data) bricks and the 
> 3rd one is the arbiter (which only holds meta data).
>
> See [1] for some discussions. What does everyone feel is more user 
> friendly and intuitive?
>
> Thanks,
> Ravi
>
> [1] https://github.com/gluster/glusterd2/pull/480
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users

I think the replica 2 arbiter 1 is more clear towards the intent of the
configuration.
I would also support :
replica n <brick 1>,<brick 2>,...,<brick n> arbiter m
<brick 1>,<brick
2>,...<brick m>
as that makes it very clear what brick(s) should be the arbiter(s).
On Wed, 2017-12-20 at 15:44 +0530, Ravishankar N wrote:
> Hi,
> 
> The existing syntax in the gluster CLI for creating arbiter volumes
> is 
> `gluster volume create <volname> replica 3 arbiter 1 <list of
> bricks>` . 
> It means (or at least intended to mean) that out of the 3 bricks, 1 
> brick is the arbiter.
> There has been some feedback while implementing arbiter support in 
> glusterd2 for glusterfs-4.0 that we should change this to `replica 2 
> arbiter 1` , meaning that there are 2 replica (data) bricks and the
> 3rd 
> one is the arbiter (which only holds meta data).
> 
> See [1] for some discussions. What does everyone feel is more user 
> friendly and intuitive?
> 
> Thanks,
> Ravi
> 
> [1] https://github.com/gluster/glusterd2/pull/480
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
-- 
James P. Kinney III

Every time you stop a school, you will have to build a jail. What you
gain at one end you lose at the other. It's like feeding a dog on his
own tail. It won't fatten the dog.
- Speech 11/23/1900 Mark Twain

http://heretothereideas.blogspot.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20171220/fcd611c1/attachment.html>

Thanks wk, Jim and Shyam for the feedback.? Let us go with `replica 2 
arbiter 1` in that case.

@Shyam, There are no plans to make arbiter count more than 1, but I 
think it is better to have it stated explicitly. If we are not going 
with a new volume type but? say `replica 2 arbiter` and give 3 brick 
paths, it can be confusing, so sticking to `replica 2 arbiter 1 for now.

Regards,
Ravi

On 12/20/2017 03:44 PM, Ravishankar N wrote:
> Hi,
>
> The existing syntax in the gluster CLI for creating arbiter volumes is 
> `gluster volume create <volname> replica 3 arbiter 1 <list of
bricks>`
> . It means (or at least intended to mean) that out of the 3 bricks, 1 
> brick is the arbiter.
> There has been some feedback while implementing arbiter support in 
> glusterd2 for glusterfs-4.0 that we should change this to `replica 2 
> arbiter 1` , meaning that there are 2 replica (data) bricks and the 
> 3rd one is the arbiter (which only holds meta data).
>
> See [1] for some discussions. What does everyone feel is more user 
> friendly and intuitive?
>
> Thanks,
> Ravi
>
> [1] https://github.com/gluster/glusterd2/pull/480
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users