Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-78545

CheckMetadataConsistency hook should retry on FailedToSatisfyReadPreference

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.0-rc7
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v7.0
    • Sharding EMEA 2023-07-10
    • 150

      When there is a stepdown, and there is no stepup for more than 15 seconds, CheckMetadataConsistency hook will throw a FailedToSatisfyReadPreference. This can happen with slow machines, when the node is slow in shutting down, and the cluster remains without a primary for a long time.

      As the CheckMetadataConsistency hook is continuously being run, I propose to abort the hook if a FailedToSatisfyReadPreference error is found.

            Assignee:
            pol.pinol@mongodb.com Pol Pinol
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: