[Gluster-users] Replication logic
oracle at provocation.net
Sat Dec 26 20:43:16 UTC 2020
I'm new to gluster and to this list too and, as is to be expected,
I come with questions.
I have set up a replica 3 arbiter 1 volume. Is there a way to turn
the arbiter into a full replica without breaking the volume and
losing the metadata that is already on the arbiter?
Given a normal (not geo) replica 3 volume like this
where brick2<->brick3 is a high-speed connection, but brick1<->brick2
and brick1<->brick3 are low speed, and data is fed to brick1, is there
a way to tell the volume that brick1 should only feed brick2 and let
brick2 feed brick3 if (and only if) all three are online, rather than
brick1 feeding both brick2 and brick3?
I realise that taking brick3 offline during a data burst and then back
online would approximate this effect, but my question is about a
permanent arrangement, something like priorities or weights.
If there is no way to configure this, does brick1 in the default
behaviour send all files sequentially to both other bricks, or does
it initially send different files to each of them, so that they get
a chance to also share between themselves?
More information about the Gluster-users