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 "Francesco Mari (JIRA)" <ji...@apache.org> on 2016/03/07 13:29:40 UTC
[jira] [Resolved] (OAK-4089) The standby store shouldn't start the
observation subsystem
[ https://issues.apache.org/jira/browse/OAK-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Mari resolved OAK-4089.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.6)
1.5.0
Fixed in r1733913.
> The standby store shouldn't start the observation subsystem
> -----------------------------------------------------------
>
> Key: OAK-4089
> URL: https://issues.apache.org/jira/browse/OAK-4089
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: tarmk-standby
> Reporter: Francesco Mari
> Assignee: Francesco Mari
> Fix For: 1.5.0
>
>
> The current implementation of {{SegmentNodeStore}} unconditionally instantiates a {{ChangeDispatcher}} referencing the root node of the repository at the time of instantiation.
> When this occurs in the context of the standby store, the {{ChangeDispatcher}} is never notified for changes in the repository content, and the initial repository root is permanently referenced by the {{ChangeDispatcher}}. This prevents many segments from being correctly cleaned up from the standby store.
> It would be more appropriate not to instantiate the observation subsystem at all in the context of the standby store, thus preventing spurious references to {{SegmentId}} instances to float in memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)