jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Egli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3672) SegmentDiscoveryLiteService does not persist clusterView.id
Date Wed, 27 Jan 2016 16:30:40 GMT

    [ https://issues.apache.org/jira/browse/OAK-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119708#comment-15119708

Stefan Egli commented on OAK-3672:

SLING-5458 is in the Sling release process - expected to be publicly released not-before JAN-30
5pm UTC

> 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
>            Assignee: 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

View raw message