-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:None
Description
Added new metric under shardingStatistics.catalogCache that will only be incremented on mongos:
https://docs.mongodb.com/manual/reference/command/serverStatus/#shardingstatistics
It will be the field OperationsBlockedByRefresh, which will be a container with six counts:
OperationsBlockedByRefresh.countAllOperations
OperationsBlockedByRefresh.countInserts
OperationsBlockedByRefresh.countQueries
OperationsBlockedByRefresh.countUpdates
OperationsBlockedByRefresh.countDeletes
OperationsBlockedByRefresh.countCommands
This metric will track any operations that flow through the mongos/router and had to block on a catalog cache refresh during the operation.
This metric will be backported back to 4.2.
Top-level view:
"shardingStatistics" : { "catalogCache" : { "numDatabaseEntries" : NumberLong(<num>), "numCollectionEntries" : NumberLong(<num>), "countStaleConfigErrors" : NumberLong(<num>), "totalRefreshWaitTimeMicros" : NumberLong(<num>), "numActiveIncrementalRefreshes" : NumberLong(<num>), "countIncrementalRefreshesStarted" : NumberLong(<num>), "numActiveFullRefreshes" : NumberLong(<num>), "countFullRefreshesStarted" : NumberLong(<num>), "countFailedRefreshes" : NumberLong(<num>), "operationsBlockedByRefresh" : { "countAllOperations" : NumberLong(<num>), "countInserts" : NumberLong(<num>), "countQueries" : NumberLong(<num>), "countUpdates" : NumberLong(<num>), "countDeletes" : NumberLong(<num>), "countCommands : NumberLong(<num>), } } },
Description of Linked Ticket
Text from scope document:
"Count and percentage of number of queries that are no longer blocked, but would have been blocked on a refresh"
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
- documents
-
SERVER-46396 Add metrics to track number of operations blocked behind a catalog cache refresh
- Closed