[ https://issues.apache.org/jira/browse/OAK-9392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated OAK-9392: ---------------------------------- Fix Version/s: 1.22.8 > 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, 1.22.8 > > > 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)