search for: arbiter2

After force the add-brick gluster volume add-brick VMS replica 3 arbiter 1 arbiter:/arbiter1 arbiter:/arbiter2 arbiter:/arbiter3 force volume add-brick: success pve01:~# gluster volume info Volume Name: VMS Type: Distributed-Replicate Volume ID: e1a4f787-3f62-441e-a7ce-c0ae6b111ebf Status: Started Snapshot Count: 0 Number of Bricks: 3 x (2 + 1) = 9 Transport-type: tcp Bricks: Brick1: gluster1:/disco2TB-0/v...

What's the volume structure right now? Best Regards, Strahil Nikolov On Wed, Nov 6, 2024 at 18:24, Gilberto Ferreira<gilberto.nunes32 at gmail.com> wrote: So I went ahead and do the force (is with you!) gluster volume add-brick VMS replica 3 arbiter 1 arbiter:/arbiter1 arbiter:/arbiter2 arbiter:/arbiter3 volume add-brick: failed: Multiple bricks of a replicate volume are present on the same server. This setup is not optimal. Bricks should be on different nodes to have best fault tolerant co nfiguration. Use 'force' at the end of the command if you want to override this beh...

So I went ahead and do the force (is with you!) gluster volume add-brick VMS replica 3 arbiter 1 arbiter:/arbiter1 arbiter:/arbiter2 arbiter:/arbiter3 volume add-brick: failed: Multiple bricks of a replicate volume are present on the same server. This setup is not optimal. Bricks should be on different nodes to have best fault tolerant co nfiguration. Use 'force' at the end of the command if you want to override this beh...

But if I change replica 2 arbiter 1 to replica 3 arbiter 1 gluster volume add-brick VMS replica 3 arbiter 1 arbiter:/arbiter1 arbiter:/arbiter2 arbiter:/arbiter3 I got thir error: volume add-brick: failed: Multiple bricks of a replicate volume are present on the same server. This setup is not optimal. Bricks should be on different nodes to have best fault tolerant configuration. Use 'force' at the end of the command if you want to...

...hat. In this new server, I have a small disk like 480G in size. And I created 3 partitions formatted with XFS using imaxpct=75, as suggested in previous emails. And than in the gluster nodes, I tried to add the brick gluster vol add-brick VMS replica 3 arbiter 1 arbiter:/arbiter1/arbiter1 arbiter:/arbiter2/arbiter2 arbiter:/arbiter3/arbiter3 But to my surprise (or not!) I got this message: volume add-brick: failed: Multiple bricks of a replicate volume are present on the same server. This setup is not optimal. Bricks should be on different nodes to have best fault tolerant co nfiguration. Use 'f...

...e a small disk like 480G in size. > And I created 3 partitions?formatted?with XFS using?imaxpct=75, as > suggested in previous emails. > > And than in the gluster nodes, I tried to add the brick > gluster vol add-brick VMS replica 3 arbiter 1 > arbiter:/arbiter1/arbiter1 arbiter:/arbiter2/arbiter2 > arbiter:/arbiter3/arbiter3 > > But to my surprise (or not!) I got this message: > volume add-brick: failed: Multiple bricks of a replicate volume are > present on the same server. This setup is not optimal. Bricks should > be on different nodes to have best fault toler...

...ed 3 partitions?formatted?with XFS using?imaxpct=75, > > > as suggested in previous emails. > > > > > > And than in the gluster nodes, I tried to add the brick > > > gluster vol add-brick VMS replica 3 arbiter 1 > > > arbiter:/arbiter1/arbiter1 arbiter:/arbiter2/arbiter2 > > > arbiter:/arbiter3/arbiter3 > > > > > > But to my surprise (or not!) I got this message: > > > volume add-brick: failed: Multiple bricks of a replicate volume > > > are present on the same server. This setup is not optimal. Bricks > &gt...

...ve a small disk like 480G in size. > And I created 3 partitions formatted with XFS using imaxpct=75, as > suggested in previous emails. > > And than in the gluster nodes, I tried to add the brick > gluster vol add-brick VMS replica 3 arbiter 1 arbiter:/arbiter1/arbiter1 > arbiter:/arbiter2/arbiter2 arbiter:/arbiter3/arbiter3 > > But to my surprise (or not!) I got this message: > volume add-brick: failed: Multiple bricks of a replicate volume are > present on the same server. This setup is not optimal. Bricks should be on > different nodes to have best fault tolerant co...

...gt; volume add-brick: failed: Operation failed > pve01:~# gluster vol add-brick VMS replica 3 arbiter 1 > gluster1:/disco2TB-0/vms gluster2:/disco2TB-0/vms gluster1:/disco1TB-0/vms > gluster2:/disco1TB-0/vms gluster1:/disco1TB-1/vms gluster2: > /disco1TB-1/vms arbiter:/arbiter1 arbiter:/arbiter2 arbiter:/arbiter3 > arbiter:/arbiter4 > volume add-brick: failed: Operation failed > > --- > > > Gilberto Nunes Ferreira > > > > > > > > Em ter., 5 de nov. de 2024 ?s 13:39, Andreas Schwibbe <a.schwibbe at gmx.net> > escreveu: > > > If...

...e72a4bfd gluster1.home.local Connected 99ed1f1e-7169-4da8-b630-a712a5b71ccd gluster2 Connected 4718ead7-aebd-4b8b-a401-f9e8b0acfeb1 localhost Connected But when I do this: pve01:~# gluster volume add-brick VMS replica 2 arbiter 1 arbiter:/arbiter1 arbiter:/arbiter2 arbiter:/arbiter3 I got this error: For arbiter configuration, replica count must be 3 and arbiter count must be 1. The 3rd brick of the replica will be the arbiter Usage: volume add-brick <VOLNAME> [<replica> <COUNT> [arbiter <COUNT>]] <NEW-BRICK> ... [force] glust...

...rick: failed: Operation failed >> pve01:~# gluster vol add-brick VMS replica 3 arbiter 1 >> gluster1:/disco2TB-0/vms gluster2:/disco2TB-0/vms gluster1:/disco1TB-0/vms >> gluster2:/disco1TB-0/vms gluster1:/disco1TB-1/vms gluster2: >> /disco1TB-1/vms arbiter:/arbiter1 arbiter:/arbiter2 arbiter:/arbiter3 >> arbiter:/arbiter4 >> volume add-brick: failed: Operation failed >> >> --- >> >> >> Gilberto Nunes Ferreira >> >> >> >> >> >> >> >> Em ter., 5 de nov. de 2024 ?s 13:39, Andreas Schwibbe &lt...

Right now you have 3 "sets" of replica 2 on 2 hosts.In your case you don't need so much space for arbiters (10-15GB with 95 maxpct is enough for each "set") and you need a 3rd system or when the node that holds the data brick + arbiter brick fails (2 node scenario) - that "set" will be unavailable. If you do have a 3rd host, I think the command would be:gluster