[
https://issues.apache.org/jira/browse/OAK-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029667#comment-15029667
]
Michael Dürig commented on OAK-3672:
------------------------------------
That one is an instance id that is not persisted and not guaranteed to be
stable across restarts: its contract is: "... will return a unique number per
instance across the cluster. It will only make its best effort to preserve the
same number across restarts but it must be unique across the cluster."
The main reason for not making it stable across restarts where the troublesome
semantics that go along with it: what about cloning/backing up/restoring a
repository?
> SegmentDiscoveryLiteService does not persist clusterView.id
> -----------------------------------------------------------
>
> Key: OAK-3672
> URL: https://issues.apache.org/jira/browse/OAK-3672
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segmentmk
> Affects Versions: 1.3.10
> Reporter: Stefan Egli
> Fix For: 1.4
>
>
> The discovery-lite-descriptor introduced with OAK-2844 has a property {{id}}
> that uniquely and persistently identifies a cluster. However, the
> {{SegmentDiscoveryLiteService}} creates this id upon each instance restart
> (by setting {{runtimeClusterId}}).
> This should be fixed to have this {{id}} persisted somehow.
> Note that the consequences of this id changing upon each restart is that the
> corresponding presumed-to-be-persistent {{ClusterView.id}} of the
> discovery.oak will also change upon restart. Which is a violation of the
> discovery API and upper level applications might thus misbehave in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
