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

Ensure vector clock is recovered on step-up

    • Fully Compatible
    • v5.2, v5.0
    • Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10

      Ticket coming from this comment of SERVER-55032.

      Tasks to be performed before 6.0 gets released:

      • Run VectorClock::recover() (in addition to the ShardingStateRecovery::recover()) on stepup
      • In ShardingStateRecovery::endMetadataOp(), also make configTime durable on VectorClock

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: