-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Sharding EMEA
-
Fully Compatible
-
ALL
-
v6.0, v5.0, v4.4
-
Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06
The operationsBlockedByRefresh counters are increased on mongos for every operation that use collection routing information even if the operation haven't been blocked by a catalog refresh.
In fact all operations that requires collection routing information end up calling CatalogCache::_getCollectionPlacementInfoAt . In this function we unconditionally set the operationBlockedBheindCatalogCacheRefres boolean to true and when the operation completes we execute CatalogCache::checkAndRecordOperationBlockedByRefresh that increase the metric counters.
This metric has been introduced by SERVER-46396 as part of PM-1633. The future flag for this project have been disabled because we discovered was causing performance regression.
This goal of this ticket is to remove this wrong and misleading metric to avoid confusion.
- is caused by
-
SERVER-46396 Add metrics to track number of operations blocked behind a catalog cache refresh
-
- Closed
-
- is depended on by
-
-
- Closed
-
- is documented by
-
DOCS-15949 Investigate changes in SERVER-73394: Remove misleading operationsBlockedByRefresh metrics
-
- Closed
-