Get rid of RecoveryDocument

XMLWordPrintableJSON

    • Sharding EMEA
    • Sharding EMEA 2021-10-18
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The RecoveryDocument is currently tracking the minOpTime to ensure v4.4 compatibility: not having it would be a problem when downgrading from v4.6 to v4.4 or in case of mixed mongod versions.

      Since - starting from v4.6 - the VectorClock persistence/recovery is ensuring casual consistency of the configOpTime, the RecoveryDocument can just be deleted starting from next versions.

              Assignee:
              [DO NOT USE] Backlog - Sharding EMEA
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: