The ClusterNodeInfo is responsible for assigning a clusterId to a DocumentNodeStore on startup. The current implementation uses the lowest MAC address available on the system and the working directory as information to reuse a previously assigned clusterId. This ensures a DocumentNodeStore gets the same clusterId after a restart.
For static deployments this works fine, but become a problem when deployments are more dynamic. Consider a cluster deployed on container infrastructure. Scaling the application may mean cluster nodes are added or removed over time and deployed on various types of machines depending on current load and required resources. Over time more and more unused clusterIds would exist and and bloat underlying documents in the DocumentStore.
This issue proposes a more greedy algorithm when a clusterId is assigned to a DocumentNodeStore.