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 "Miroslav Smiljanic (Jira)" <ji...@apache.org> on 2021/06/03 14:54:06 UTC

[jira] [Closed] (OAK-9392) Improve resilience when primary becomes unavailable

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

Miroslav Smiljanic closed OAK-9392.
-----------------------------------

> Improve resilience when primary becomes unavailable
> ---------------------------------------------------
>
>                 Key: OAK-9392
>                 URL: https://issues.apache.org/jira/browse/OAK-9392
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Major
>             Fix For: 1.40.0
>
>
> Every now and then I observe cases where a MongoDB primary becomes unavailable, one of the secondary becomes the new primary rather quickly, but Oak is still unable to update its lease in the clusterNodes collection and then needs to be restarted. It appears, the lease update can be stuck and waiting for a response from the failing primary, e.g. due to a network issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)