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

nShards metric includes shards which produced StaleConfigException and were subsequently de-targeted

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 3.7.4, 4.0.0-rc4
    • Component/s: Logging, Sharding
    • Query Execution
    • ALL
    • v4.0

      On mongos, we log the number of shards involved in an operation via the nShards metric. However, in the mongoS write path (and possible elsewhere), if a shard returns a StaleConfig exception and is not present in the set of shards re-targeted by the mongoS after it refreshes its routing table, we still include the shard in the nShards count.

            Assignee:
            backlog-query-execution [DO NOT USE] Backlog - Query Execution
            Reporter:
            bernard.gorman@mongodb.com Bernard Gorman
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: