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

Checkpoint the vector clock when discovering new shard versions

    XMLWordPrintableJSON

Details

    • Catalog and Routing
    • Sharding EMEA 2022-02-21, Sharding EMEA 2022-03-07, Sharding EMEA 2022-03-21, Sharding EMEA 2022-04-04, Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02
    • 1.5

    Description

      Persisting the vector clock before setting the filtering metadata discovered after refreshing ensures causal consistency in the following scenario:

      • Node A is primary and refreshes, discovering shard version X
      • Step-down
      • Node B becomes primary and refreshes, discovering shard version X - 1 because reading from the (stale) nearest CSRS node

      In order to not block the shard for too long of a time, the checkpoint must be done only with local write concern.

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: