[
https://issues.apache.org/jira/browse/OAK-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Jain updated OAK-1849:
---------------------------
Attachment: OAK-1849.patch
Patch implementing ideas above. Please review.
There are few points in particular where more discussion is needed:
# Introduced a new interface {{SharedDataStore}} which all supporting data
stores would implement if they support the shared access. Should this interface
be in jackrabbit as {{S3DataStore}} may also need to implement this? Currently,
I have it as part of Oak so thats its easier to review.
# The only implementation currently is in {{OakFileDataStore}}. Is this ok or
should be moved to the {{FileDataStore}}?
# The current implementation for a unique cluster {{repositoryId}} keeps it as
a property {{:clusterId}} in a new node {{/:clusterConfig}}. This information
is registered in the node/data stores in the {{*NodeStoreService}}. The
{{repositoryId}} is used to register different clusters in the DataStore as
well as identify the references from the cluster that are kept at the root of
the DataStore.
> DataStore GC support for heterogeneous deployments using a shared datastore
> ---------------------------------------------------------------------------
>
> Key: OAK-1849
> URL: https://issues.apache.org/jira/browse/OAK-1849
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Amit Jain
> Attachments: OAK-1849.patch
>
>
> If the deployment is such that there are 2 or more different instances with a
> shared datastore, triggering Datastore GC from one instance will result in
> blobs used by another instance getting deleted, causing data loss.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
