[COMPASS-6589] Investigate changes in SERVER-73394: Remove misleading operationsBlockedByRefresh metrics Created: 07/Mar/23 Updated: 24/Aug/23 Resolved: 03/May/23 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Investigation | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | COMPASS-5987 | ||||||||
| Documentation Changes: | Not Needed | ||||||||
| Description |
|
Original Downstream Change Summary Removed operationsBlockedByRefresh metrics of serverStatus: Description of Linked TicketThe 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 |
| Comments |
| Comment by PM Bot [ 24/Aug/23 ] |
|
Fix Version updated for upstream |
| Comment by PM Bot [ 24/Aug/23 ] |
|
Fix Version updated for upstream |
| Comment by PM Bot [ 17/Aug/23 ] |
|
Fix Version updated for upstream |