[ https://issues.apache.org/jira/browse/OAK-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989738#comment-14989738 ]
Julian Reschke commented on OAK-3449: ------------------------------------- ...actually, it's a series of changes. 1.2 and 1.0 do not have the change yet (there was a change but I backed it out when encountering problems) I'll review what we have in trunk and whether we can close the issue (I recall there's something left to do...) > DocumentNodeStore support for predefined clusterIds should use > ClusterNodeInfos > ------------------------------------------------------------------------------- > > Key: OAK-3449 > URL: https://issues.apache.org/jira/browse/OAK-3449 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core, mongomk, rdbmk > Affects Versions: 1.0.21, 1.3.6, 1.2.6 > Reporter: Julian Reschke > Assignee: Julian Reschke > Labels: test > Attachments: OAK-3449.diff, cid.diff > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)