[SERVER-35505] nShards metric includes shards which produced StaleConfigException and were subsequently de-targeted Created: 08/Jun/18  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Logging, Sharding
Affects Version/s: 3.7.4, 4.0.0-rc4
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Bernard Gorman Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-34016 Add number of contacted shards to the... Closed
Assigned Teams:
Query Execution
Operating System: ALL
Backport Requested:
v4.0
Participants:

 Description   

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.


Generated at Thu Feb 08 04:40:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.