jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amit Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3935) SharedDataStore - Allow unique repository ID to be specified by config
Date Tue, 02 Feb 2016 07:00:46 GMT

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

Amit Jain commented on OAK-3935:
--------------------------------

[~mduerig] 
bq. 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.
It does not because nothing is to be done in these cases. Only when a system is cloned it
creates problems as the Id generated has to be different which can be overridden by config
{{sharedDSRepoId}}

> 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)

Mime
View raw message