-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Diagnostics, Querying, Sharding
-
Fully Compatible
-
Sharding EMEA 2022-06-13, Sharding EMEA 2022-06-27, Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25, Sharding EMEA 2022-08-08, Sharding EMEA 2022-08-22, Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03
-
6
When mongos and mongod are performing sharding metadata refresh CRUD operations are getting blocked, unfortunately this time is not currently logged in the CRUD operation log but we need to correlate that with refresh logs like:
2021-04-23T13:04:35.737+0200 I SH_REFR [ConfigServerCatalogCacheLoader-17] Refresh for collection adap.LinesEnhanced from version 98568|42||5fb3e9d4d35c25a2b0dd61ab to version 98568|45||5fb3e9d4d35c25a2b0dd61ab took 885 ms
The total time that the CRUD operation is waiting should be added to the query log
- related to
-
SERVER-67252 Track time spent waiting for refresh on the shards
- Closed
-
SERVER-67253 Track time spent waiting for refresh on the router
- Closed
-
SERVER-68851 Remove wait for collection critical section from service entry point
- Closed
-
SERVER-69225 Remove wait for database critical section from service entry point
- Closed