Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-9392

Improve resilience when primary becomes unavailable

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.40.0, 1.22.8
    • mongomk
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              mreutegg Marcel Reutegger
              mreutegg Marcel Reutegger
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: