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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2018/09/18 08:21:00 UTC

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

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

Thomas Mueller updated OAK-6950:
--------------------------------
    Summary: Active deletion can delete blobs from a shared datastore when a clone setup is created  (was: Active deletion can delete blobs from a shared store when a clone setup is created)

> Active deletion can delete blobs from a shared datastore 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
>            Priority: Major
>             Fix For: 1.7.14, 1.8.0
>
>         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
(v7.6.3#76005)