Shard can crash at step-up due to FailedToSatisfyReadPreference exception during minOpTime recovery

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • ALL
    • 8
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The ReplicationCoordinatorExternalStateImpl::_shardingOnTransitionToPrimaryHook call already expects NotMaster and ShutdownInProgress errors, but it can also crash in certain cases with a FailedToSatisfyReadPreference exception if the config server is not available at shard node's step-up time.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: