Make ShardRegistry remember the operationTime of the config server read from its last reload

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Repl 2017-09-11
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      ChangeStreams needs to be able to know how up-to-date the data in the ShardRegistry is in terms of cluster time. When the shard registry does a read against config.shards as part of its internal reload, it should remember the operationTime returned by that read.

            Assignee:
            Nathan Myers (Inactive)
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: