CheckMetadataConsistency hook should retry on FailedToSatisfyReadPreference

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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
              Reporter:
              Pol Pinol
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: