[
https://issues.apache.org/jira/browse/OAK-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123340#comment-15123340
]
Michael Dürig commented on OAK-3935:
------------------------------------
Stefan is probably in the better position to comment on the Sling aspect.
However, we should be careful with introducing global repository/cluster/node
ids without carefully clarifying its semantics. The {{sharedDSRepoId}} as it
stands introduces additional operational complexities for
backup/restore/sidegrade etc.
OAK-3529 recently introduced something similar. There we purposefully do not
guarantee uniqueness across restarts to avoid the problems arising from
cloning.
> SharedDataStore - Allow unique repository ID to be specified by config
> -----------------------------------------------------------------------
>
> Key: OAK-3935
> URL: https://issues.apache.org/jira/browse/OAK-3935
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob, segmentmk
> Reporter: Amit Jain
> Assignee: Amit Jain
> Labels: resilience
> Fix For: 1.2.11, 1.3.15
>
> Attachments: OAK-3935-sling-settings.patch
>
>
> For GC in a shared DataStore, a unique repository Id is currently saved in a
> hidden path in the node store on startup and registered in the DataStore.
> This will cause problems where the publish environments are cloned and share
> a datastore.
> There should be an option to specify a unique id in the config when setting
> up the node store.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
