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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/06/21 06:51:57 UTC

[jira] [Updated] (OAK-4490) Expose SegmentNodeStore as a secondary NodeStore

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

Chetan Mehrotra updated OAK-4490:
---------------------------------
    Attachment: OAK-4490-v1.patch

[initial patch|^OAK-4490-v1.patch]. With this patch

# {{SegmentNodeStoreService}} exposes a new boolean config option {{secondary}}. 
# If above option is enabled then a {{SegmentNodeStore}} instance is registered with service property {{type}} set to {{secondary}}
# Also in this mode NodeStore would not be looking for Observor, exposing any GC MBean etc

[~alex.parvulescu] [~frm] [~mduerig] Can you review the approach and provide feedback. If approach looks fine I can work on test and also a variant for segment-tar

Also if approach looks fine I would work on proposal to ensure that other parts of Oak where we look NodeStore does not get confused and bind to correct NodeStore

/cc [~mreutegg]

> Expose SegmentNodeStore as a secondary NodeStore
> ------------------------------------------------
>
>                 Key: OAK-4490
>                 URL: https://issues.apache.org/jira/browse/OAK-4490
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: segment-tar, segmentmk
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.6
>
>         Attachments: OAK-4490-v1.patch
>
>
> For OAK-4180 to work we would need to configure a SegmentNodeStore as a secondary NodeStore. This NodeStore instance is used as a local cache of remote content for certain paths. 
> Point to note
> # The NodeStore instance would be full functional except it would not be registering any Observor 
> # With this its possible to have a setup where multiple NodeStore instances are registered in same service registry. So it needs to be ensure that any other component which depends on NodeStore binds to correct store



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)