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 "Julian Reschke (JIRA)" <ji...@apache.org> on 2015/09/23 15:20:04 UTC

[jira] [Commented] (OAK-3420) DocumentNodeStoreService fails to restart DocumentNodeStore

    [ https://issues.apache.org/jira/browse/OAK-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904490#comment-14904490 ] 

Julian Reschke commented on OAK-3420:
-------------------------------------

After discussion with [~chetanm] it's not clear that there is a use case for a restart. Thus we should focus that the DocumentNodeStoreService does not even attempt the restart.

> DocumentNodeStoreService fails to restart DocumentNodeStore
> -----------------------------------------------------------
>
>                 Key: OAK-3420
>                 URL: https://issues.apache.org/jira/browse/OAK-3420
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Julian Reschke
>              Labels: resilience
>         Attachments: DocumentNodeStoreConfigTest.groovy
>
>
> Scenario (test case will follow):
> 1) service configured for RDBDocumentStore with DataSources
> 2) gets started
> 3) DataSource unregisters, DocumentNodeStore gets shut down
> 4) DataSource is registered again
> 5) restart of DocumentNodeStore fails with NPE because at least one required component (executor?) now is null
> We need to decide whether this is a scenario that should be supported or not. If yes, we need to fix it. If no, we need to make the code more robust and improve diagnostics.



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