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

SessionsCollectionConfigServer::_shardCollectionIfNeeded swallows all types of errors

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • ALL
    • Sharding NYC 2023-06-12, Sharding NYC 2023-06-26
    • 0
    • 3

      Currently it assumes the possible error it can get is because due to collection not being sharded here. This means that other types of errors, like interrupt or repl set transition errors will be swallowed and be allow it to proceed and shard the collection.

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: