You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Amit Jain (JIRA)" <ji...@apache.org> on 2018/10/04 09:47:00 UTC

[jira] [Resolved] (OAK-7776) Ignore copying of :clusterConfig in InitialContentMigrator

     [ https://issues.apache.org/jira/browse/OAK-7776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amit Jain resolved OAK-7776.
----------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.9.10)
                   1.9.9

> Ignore copying of :clusterConfig in InitialContentMigrator
> ----------------------------------------------------------
>
>                 Key: OAK-7776
>                 URL: https://issues.apache.org/jira/browse/OAK-7776
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: Amit Jain
>            Assignee: Amit Jain
>            Priority: Major
>             Fix For: 1.10, 1.9.9
>
>
> :clusterConfig entry which stores the latest clusterId/repositoryId used for registering the repository in the DataStore gets wiped out for the global store if content is migrated by InitialContentMigrator. The consequence of this is that there are multiple repositoryId created at unexpected times and also files corresponding to them created in the DataStore which would block DSGC.
> This should be excluded when copying to the target store as that store would be the main/writable one. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)