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 "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/09/14 10:29:45 UTC

[jira] [Updated] (OAK-3250) Restart DocumentNodeStore on lease timeout instead of System.exit

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

Stefan Egli updated OAK-3250:
-----------------------------
    Fix Version/s:     (was: 1.3.6)
                   1.4

Unscheduling this from 1.3 for now as we should follow-up on OAK-3397 as the short-to-medium term solution (long-term we might be able to come back to OAK-3250)

> Restart DocumentNodeStore on lease timeout instead of System.exit
> -----------------------------------------------------------------
>
>                 Key: OAK-3250
>                 URL: https://issues.apache.org/jira/browse/OAK-3250
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.3.4
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: 1.4
>
>
> As discussed [on the list|http://markmail.org/thread/uo6n5oozlbhe7ifg] usage of System.exit is not ideal and one suggested alternative is to follow up on the idea to instead perform a 'restart of DocumentNodeStore' - while marking the local instance as 'deactivating' towards discovery-lite-descriptor so that upper layer discovery.oak can properly send a TOPOLOGY_CHANGING to all listeners, so that they immediately stop any topology-dependent activity.



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