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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2015/09/08 10:35:46 UTC

[jira] [Commented] (OAK-2265) DocumentNodeStore service should go away if MongoDB becomes unavailable

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

Marcel Reutegger commented on OAK-2265:
---------------------------------------

The second use case will be covered by OAK-3250. If MongoDB or more generally the DocumentStore backend is unavailable beyond the lease time, the DocumentNodeStore should be restarted.

> DocumentNodeStore service should go away if MongoDB becomes unavailable
> -----------------------------------------------------------------------
>
>                 Key: OAK-2265
>                 URL: https://issues.apache.org/jira/browse/OAK-2265
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Bertrand Delacretaz
>
> Stopping the MongoDB backend that a Sling instance is using via the DocumentNodeStore service should cause that OSGi service to be unregistered.
> Currently the service stays registered even if MongoException$Network is thrown when trying to access the MongoDB backend.
> The code that manages the service should ping the backend and register/unregister the DocumentNodeStore to follow the backend's availablity. This will allow other services that depend on DocumentNodeStore to restart correctly once MongoDB is available again.



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