[SERVER-59658] Improve logging to reflect that sharding metadata refresh waiting on replication - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Closed
Priority: Major - P3
Resolution: Fixed
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
Component/s: None
Labels:
- sharding-slow-logging
- shardingemea-qw

Backwards Compatibility:
Fully Compatible
Backport Requested:

v6.0, v5.3, v5.0, v4.4, v4.2
Sprint:
Sharding EMEA 2022-06-13
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?

Attachments

Activity

People

Assignee:: Allison Easton

Reporter:: Dmitry Ryabtsev

Participants:: Allison Easton, Dmitry Ryabtsev, Githook User

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: Aug 28 2021 12:03:05 AM UTC

Updated:: Jun 21 2022 08:16:42 AM UTC

Resolved:: Jun 08 2022 01:54:02 PM UTC