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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2017/12/17 23:14:00 UTC

[jira] [Resolved] (OAK-6950) Active deletion can delete blobs from a shared store when a clone setup is created

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

Vikas Saurabh resolved OAK-6950.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.13

Fixed on trunk at [r1818521|https://svn.apache.org/r1818521].

> Active deletion can delete blobs from a shared store when a clone setup is created
> ----------------------------------------------------------------------------------
>
>                 Key: OAK-6950
>                 URL: https://issues.apache.org/jira/browse/OAK-6950
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>             Fix For: 1.7.13, 1.8
>
>         Attachments: OAK-6950.wip.1.patch
>
>
> It's a common scenario have multiple seg-tar instance to load balance. These instance often share the data-store.
> Provisioning of such instance is often done by preare one instance and clone new ones from this instance.
> In such cases, index files while were live at the time of cloning can be collected by one instance while still being required by the other.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)