[
https://issues.apache.org/jira/browse/OAK-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-3935:
---------------------------------
Attachment: OAK-3935-sling-settings.patch
[proposed patch|^OAK-3935-sling-settings.patch] which makes an attempt to
determine the repositoryId via {{SlingSettingsService}} if present in the OSGi
Service Registry
Dependency on {{SlingSettingsService}} is optional. This would allow simpler
usage of Oak when running within Sling based systems as then admin would not
have to worry about dealing with cleaning of multiple id state while performing
a clone of existing setup.
With current config based approach we would need to document that a system user
changes the OSGi config is Oak repository folder is cloned via copy to a
different system.
[~amitj_76] Thoughts?
> 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
> 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)
