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

Find a better way of setting the shardId when throwing on getCollectionDescription

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: Sharding
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 2020-04-20

      Description

      SERVER-45781 introduced the assurance of getting the latest collection description metadata available on the shard. This implies that if the metadata is unknown, then a Stale Shard Version Exception will be thrown. As part of the Exception construction a shardId must be provided. Currently the ServiceContext is being captured at the constructor, which is being used to get the ShardingState, however, there is an invariant that can be hit if for example a server with

      --shardsvr

      does some operations before being added into a cluster.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marcos.grillo Marcos José Grillo Ramirez
              Reporter:
              marcos.grillo Marcos José Grillo Ramirez
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: