[SERVER-59658] Improve logging to reflect that sharding metadata refresh waiting on replication Created: 28/Aug/21  Updated: 29/Oct/23  Resolved: 08/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.2.15
Fix Version/s: 5.0.10, 4.4.16, 4.2.22, 6.0.0-rc11, 6.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Dmitry Ryabtsev Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: sharding-slow-logging, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Problem/Incident
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0, v5.3, v5.0, v4.4, v4.2
Sprint: Sharding EMEA 2022-06-13
Participants:
Case:
Linked BF Score: 170
Story Points: 6

 Description   

It appears to be expected behaviour that a metadata refresh initiated on a lagging secondary will be waiting for the replication to catch up to least the timestamp at which the refresh was triggered.

At this moment there is no way to infer from the messages produced by SH_REFR if a refresh was/is waiting for replication.

Can we please improve the logging detail in that regard?



 Comments   
Comment by Githook User [ 20/Jun/22 ]

Author:

{'name': 'Enrico Golfieri', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-59658 [v4.2] Improve logging to reflect that sharding metadata refresh waiting on replication
Branch: v4.2
https://github.com/mongodb/mongo/commit/3a40dc5b82be4a070fd140d422f817208b854a5c

Comment by Githook User [ 16/Jun/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-59658 Change durationMillis to duration
Branch: v5.0
https://github.com/mongodb/mongo/commit/a8a461182a30c32980658c86f29005e87a3beae4

Comment by Githook User [ 16/Jun/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-59658 Improve logging to reflect that sharding metadata refresh waiting on replication
Branch: v5.0
https://github.com/mongodb/mongo/commit/c37078a958d48659d15213f5c6a77a52925a7c9e

Comment by Githook User [ 16/Jun/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-59658 Change durationMillis to duration
Branch: v4.4
https://github.com/mongodb/mongo/commit/102b65b1c4b093da86e1922ba3dba77c43949f3b

Comment by Githook User [ 16/Jun/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-59658 Improve logging to reflect that sharding metadata refresh waiting on replication
Branch: v4.4
https://github.com/mongodb/mongo/commit/9fd5193425e8912ed4f3d463c51c00486daa125a

Comment by Githook User [ 16/Jun/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-59658 Change durationMillis to duration
Branch: v6.0
https://github.com/mongodb/mongo/commit/1bf1161e5db69fcee1aaa135b18ae6d9e10e94e5

Comment by Githook User [ 16/Jun/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-59658 Improve logging to reflect that sharding metadata refresh waiting on replication
Branch: v6.0
https://github.com/mongodb/mongo/commit/e1c5a1d2b82c10825cec6cb6833f274287437f08

Comment by Githook User [ 09/Jun/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-59658 Change durationMillis to duration
Branch: master
https://github.com/mongodb/mongo/commit/df4b732eefe0f7a5a58f6f23baa2b31b45e2a38c

Comment by Githook User [ 08/Jun/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-59658 Improve logging to reflect that sharding metadata refresh waiting on replication
Branch: master
https://github.com/mongodb/mongo/commit/7ce6d5072d1dc8b2b69f08cf60e78054fae813e1

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