search for: aribiter

...ave a master gluster cluster replica 2 > (in production I will use an arbiter and replicatied/distributed) > and the geo cluster is distributed with 2 machines. > (in production I will have the geo cluster distributed) > It's recommended to use slave also to be distribute replicate/aribiter/ec. Choosing only distribute will cause issues when of the slave node is down and a file is being synced which belongs to that node. It would not sync later. > Everything is up and running and creating files from client both > replicates and is distributed in the geo cluster. > > The...

...eplica 2 > > (in production I will use an arbiter and replicatied/distributed) > > and the geo cluster is distributed with 2 machines. > > (in production I will have the geo cluster distributed) > > > > It's recommended to use slave also to be distribute replicate/aribiter/ec. > Choosing only distribute will cause issues > when of the slave node is down and a file is being synced which belongs to > that node. It would not sync > later. > > > > Everything is up and running and creating files from client both > > replicates and is distri...

Hi all, I am planning my new gluster system and tested things out in a bunch of virtual machines. I need a bit of help to understand how geo-replication behaves. I have a master gluster cluster replica 2 (in production I will use an arbiter and replicatied/distributed) and the geo cluster is distributed with 2 machines. (in production I will have the geo cluster distributed) Everything is up

...the geo cluster is distributed with 2 machines. > > > > > > (in production I will have the geo cluster distributed) > > > > > > > > > > > > > > > > It's recommended to use slave also to be distribute > > > > replicate/aribiter/ec. > > > > > Choosing only distribute will cause issues > > > > > when of the slave node is down and a file is being synced which > > belongs > > > > to > > > > > that node. It would not sync > > > > > later. > > &...

I made a recusive diff on the upgraded arbiter. /var/lib/glusterd/vols/gds-common is the upgraded aribiter /home/marcus/gds-common is one of the other nodes still on gluster 10 diff -r /var/lib/glusterd/vols/gds-common/bricks/urd-gds-030:-urd-gds-gds-common /home/marcus/gds-common/bricks/urd-gds-030:-urd-gds-gds-common 5c5 < listen-port=60419 --- > listen-port=0 11c11 < brick-fsid=147643586306...

...he node fail? Do I dare to continue to upgrade my real cluster with the above described way? Thanks! Regards Marcus On Mon, Feb 20, 2023 at 01:42:47PM +0100, Marcus Peders?n wrote: > I made a recusive diff on the upgraded arbiter. > > /var/lib/glusterd/vols/gds-common is the upgraded aribiter > /home/marcus/gds-common is one of the other nodes still on gluster 10 > > diff -r /var/lib/glusterd/vols/gds-common/bricks/urd-gds-030:-urd-gds-gds-common /home/marcus/gds-common/bricks/urd-gds-030:-urd-gds-gds-common > 5c5 > < listen-port=60419 > --- > > listen-port=0...

...t; > > > > > > > (in production I will have the geo cluster distributed) > > > > > > > > > > > > > > > > > > > > > > It's recommended to use slave also to be distribute > > > > > > replicate/aribiter/ec. > > > > > > > Choosing only distribute will cause issues > > > > > > > when of the slave node is down and a file is being synced which > > > > belongs > > > > > > to > > > > > > > that node. It would no...

...cluster with the above described way? > > Thanks! > > Regards > Marcus > > > > On Mon, Feb 20, 2023 at 01:42:47PM +0100, Marcus Peders?n wrote: > > I made a recusive diff on the upgraded arbiter. > > > > /var/lib/glusterd/vols/gds-common is the upgraded aribiter > > /home/marcus/gds-common is one of the other nodes still on gluster 10 > > > > diff -r /var/lib/glusterd/vols/gds-common/bricks/urd-gds-030:-urd-gds-gds-common /home/marcus/gds-common/bricks/urd-gds-030:-urd-gds-gds-common > > 5c5 > > < listen-port=60419 > &gt...