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

Remove term from config server opTime tracking

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding NYC
    • Sharding 2019-11-04, Sharding 2019-11-18, Sharding 2019-12-16, Sharding 2020-01-13, Sharding 2020-02-10, Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06

      Currently nodes in a sharded cluster gossip the latest known config server majority committed opTime and use it as an afterOpTime read concern argument when reading sharded metadata from the config server to guarantee a causally consistent view. All sharded metadata reads and writes are performed with majority read and write concern, so there should be no situation where a rollback can break the causal consistency of catalog operations and it should be safe to stop tracking the term.

            Assignee:
            backlog-server-sharding-nyc [DO NOT USE] Backlog - Sharding NYC
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            2 Vote for this issue
            Watchers:
            23 Start watching this issue

              Created:
              Updated:
              Resolved: