Why is one Scalaris node marked as first?
When starting a Scalaris ring we have to mark exactly one node as the first node. This node will not try contacting any other node and simply wait for connections. It thus creates a new ring. We are currently using a command line parameter -boot_cs first true (non-empty boot server) / -scalaris first true (ordinary Scalaris nodes) to mark the first Scalaris node inside an Erlang VM as being the first (see bin/scalarisctl and dht_node:init/1).
