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 2021/06/25 06:45:00 UTC

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

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

Marcel Reutegger commented on OAK-9392:
---------------------------------------

Merged PR #302 by [~ankitaag] for backport to 1.22 branch: https://github.com/apache/jackrabbit-oak/commit/6bda3d7b169e18c861658077f083b90d2f9142a5

Thanks for your help on the backport!

> 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)