Hi David,
Hello,
I've a couple of questions on geo-replication that hopefully someone can help with:
1. If there are multiple nodes in a cluster on the master side (pushing updates to the geo-replication slave), which node actually does the pushing? Does GlusterFS decide itself automatically?
Once Geo-replication session is started, one worker will be started corresponding to each Master bricks. Each worker identifies the changes happened in respective brick and sync those changes via Mount. This way load is distributed among Master nodes. In case of Replica sub volume, one worker among the Replica group will become active and participate in the syncing. Other bricks in that Replica group will remain Passive. Passive worker will become Active if the previously Active brick goes down (This is because all Replica bricks will have the same set of changes, syncing from each worker is redundant).
2.With regard to copying SSH keys, presumably the SSH key of all master nodes should be authorized on the geo-replication client side?
Geo-replication session is established between one master node and one remote node. If Geo-rep create command is successful then,
- SSH keys generated in all master nodes - Public keys from all master nodes are copied to initiator Master node - Public keys copied to the Remote node specified in the create command - Master public keys are distributed to all nodes of remote Cluster and added to respective ~/.ssh/authorized_keys
After successful Geo-rep create command, any Master node can connect to any remote node via ssh.
Security: Command prefix is added while adding public key to remote node’s authorized_keys file, So that if anyone gain access using this key can access only gsyncd command.
``` command=gsyncd ssh-key…. ```
— regards Aravinda Vishwanathapura |
________
Community Meeting Calendar:
Schedule -
Every Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
