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

CheckMetadataConssitency hook should ignore FailedToSatisfyReadPreference errors

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sharding EMEA

      In scenarios in which some node in the cluster crashed the CheckMetadataConsistencyHook will fail with FailedToSatisfyReadPreference, instead we should ignore those.

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: