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

Get rid of ShardingStateRecovery once 5.0 branches out

    XMLWordPrintable

Details

    • Sharding EMEA 2021-10-18

    Description

      The ShardingStateRecovery machinery can be fully replaced by the waitFor* and recovery methods offered by the VectorClockMutable.

      Attachments

        Issue Links

          is depended on by

          Task - A task that needs to be done. SERVER-49973 Get rid of RecoveryDocument

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Task - A task that needs to be done. SERVER-60110 Get rid of ShardingStateRecovery once 7.0 branches out

          • Major - P3 - Major loss of function.
          • Open

          Task - A task that needs to be done. SERVER-60109 Ensure vector clock is recovered on step-up

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-60126 Complete TODO listed in SERVER-55032

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-sharding-emea Backlog - Sharding EMEA
              pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: