[
https://issues.apache.org/jira/browse/OAK-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026200#comment-15026200
]
Chetan Mehrotra commented on OAK-3672:
--------------------------------------
bq. can you please re-state the use cases which require a stable/persisted
cluster identifier?
IIRC the usecase was around using a stable clusterId for issuing cookies. The
clusterId was used to ensure that 2 different server running on same system
should be able to distinguish the cookies issues by them. Also even after
restart older cookies are honoured
> 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)
