[SERVER-12363] Record type of queries (targeted=1 shard, and #-shards) on each mongos in ServerStatus Created: 14/Jan/14  Updated: 14/Mar/17  Resolved: 05/Jun/14

Status: Closed
Project: Core Server
Component/s: Diagnostics, Sharding
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Minor - P4
Reporter: Alexander Komyagin Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: metrics, stats
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-9007 Record type of queries (targeted=1 sh... Closed
Participants:

 Description   

When optimizing the performance of a sharded system, a lot of times you would want to make sure that most (ideally all) your queries are targeted, or how many shards are queried.

An example section might look like this:

{ query: {
  { byShards: {"1": XX, "2":XX, "2":XX, .... }},
  { configDB: {reload:XX, partial:XX}},
}}
 



 Comments   
Comment by Greg Studer [ 05/Jun/14 ]

Closing - the byShards information isn't really actionable - it's not clear in a nontrivial cluster if the query distribution is skewed for other reasons. Even in the hashed shard case users often unintentionally have lots of duplicate shard keys, so not sure this is the metric that we want.

The version reload information stats are tracked in SERVER-4672.

Generated at Thu Feb 08 03:28:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.