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

Get rid of ShardingStateRecovery once 7.0 branches out

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • None
    • Sharding
    • Sharding EMEA
    • Fully Compatible
    • Sharding EMEA 2023-06-26

    Description

      Ticket coming from this comment of SERVER-55032.

      Tasks to be performed right after 7.0 gets released:

      • Change migration to no longer use ShardingStateRecovery and use just VectorClock::waitDurable
      • ShardingStateRecovery no longer reads or updates it's own configOpTime (we can just rely on VectorClock now)

      Attachments

        Activity

          People

            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: