Page History

...

1. It connects to a random node and sends the available local validation information (including the cluster tag and the Meta Storage version).
2. The following scenarios can then happen:
   1. The random node is initialized and the cluster tags do not match. The joining node must be rejected.
   2. The random node is initialized, the cluster tags match, local Meta Storage version is "smaller" than the remote. The node joins the topology and updates its Meta Storage configuration, thus ending the joining process.
   3. The random node is initialized, the cluster tags match, local Meta Storage version is "larger" than the remote. The joining node should initiate a process similar to sending the "init" command. Discussion needed: what is the expected behavior in this caseto do if another "init" command is running in parallel?
   4. The random node is empty because the cluster has not yet been initialized. The joining node should initiate a process similar to sending the "init" command. Discussion needed: what to do if another "init" command is running in parallel?
   5. The random node is empty because it hasn't finished the join process itself. In this case the random node should send a corresponding message, and the joining node should choose another random node and repeat the process.

...