Hi all, The recent clusterId-discussions around OAK-3935 together with the cloning problem it shares with discovery.oak made me rethink the current two-clusterId-approach. After some offline discussions with Thomas and Marcel I've created OAK-4006 which suggests reusing the SharedDataStore way of a hidden :clusterId property, providing a dedicated 'after clone' offline reset tool in oak-run and using that same clusterId also in discovery-lite (thus discovery.oak). This should leave us with only 1 clusterId in the stack.
Since 1.4 will be the first to support discovery.oak, and to allow for enough testing, it would be important to have this in 1.3.16. I will therefore work on a patch tomorrow and would highly appreciate comments on the approach and patch. If +1-ed It should delay 1.3.16 a few hours or a day. https://issues.apache.org/jira/browse/OAK-4006 Cheers, Stefan
