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

SessionsCollectionConfigServer::_shardCollectionIfNeeded swallows all types of errors

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Cluster Scalability
    • ALL
    • Sharding NYC 2023-06-12, Sharding NYC 2023-06-26
    • 7
    • 3

    Description

      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.

      Attachments

        Activity

          People

            backlog-server-cluster-scalability Backlog - Cluster Scalability
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: