[SERVER-56304] Log time CRUD operations spend waiting for metadata refresh Created: 23/Apr/21  Updated: 29/Oct/23  Resolved: 21/Sep/22

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

Type: Improvement Priority: Major - P3
Reporter: Renato Riccio Assignee: Allison Easton
Resolution: Fixed Votes: 2
Labels: needs-triage, sharding-slow-logging, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-67252 Track time spent waiting for refresh ... Closed
related to SERVER-67253 Track time spent waiting for refresh ... Closed
related to SERVER-68851 Remove wait for collection critical s... Closed
related to SERVER-69225 Remove wait for database critical sec... Closed
Backwards Compatibility: Fully Compatible
Sprint: 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
Participants:
Story Points: 6

 Description   

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



 Comments   
Comment by Kaloian Manassiev [ 21/Oct/21 ]

As part of this ticket we should also include the time spent waiting for the critical section.

Generated at Thu Feb 08 05:38:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.