[OAK-3449] DocumentNodeStore support for predefined clusterIds should use ClusterNodeInfos

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.21, 1.2.6, 1.3.6
• Fix Version/s: 1.2.8, 1.3.10, 1.4
• Component/s: core, mongomk, rdbmk
• Labels: test
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 25/Sep/15 11:21
• Updated: 16/Feb/21 09:53
• Resolved: 05/Nov/15 12:14

Description

We currently support explicit assignment of clusterId (builder.setClusterId()). In this case, DocumentNodeStore uses the specified cluster id and skips all code related to creating/maintaining ClusterNodeInfos.

This feature is mainly (only?) used for testing (mainly allowing multiple instances to run from the same machine/instance combination). This works, but causes the logic related to ClusterNodeInfo not to be used at all (for instance, LastRevRecovery).

So we ought to change this config option to use ClusterNodeInfo in a way that is at least similar to real-world use.

Issue Links

• blocks: OAK-3424 ClusterNodeInfo does not pick an existing entry on startup
• breaks: OAK-3499 Test failures when there is no network interface