Improve diagnostic messages for metadata reloading in shards

XMLWordPrintableJSON

    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Idea is that on (mongod) config metadata reload, there is a lot of information presented to the user - the previous version/epoch, the loaded version/epoch, the version that may have changed while we load. There's also collection vs. shard version to report.

      We currently dump much of this info to the logs, but in common cases, we could simplify. For example:

      "collection was previously unsharded, new metadata loaded with shard version XXX|YYY (collection version XXX|YYY|epoch)"
      "collection was previously at shard version XXX|YYY, now at shard version WWW|QQQ (new collection version RRR|SSS|epoch)"

      Or maybe two messages - one for shard version, one saying "collection version was loaded at version XXX|YYY|epoch".

            Assignee:
            Siyuan Zhou
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: