Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-59658

Improve logging to reflect that sharding metadata refresh waiting on replication

    XMLWordPrintable

Details

    • Fully Compatible
    • v6.0, v5.3, v5.0, v4.4, v4.2
    • Sharding EMEA 2022-06-13
    • 170
    • 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

            allison.easton@mongodb.com Allison Easton
            dmitry.ryabtsev@mongodb.com Dmitry Ryabtsev
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: