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

Need general method to handle in-memory state after initial sync

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.0.0-rc4, 5.0.10, 6.1.0-rc0
    • None
    • None
    • Fully Compatible
    • v6.0, v5.3, v5.0
    • Repl 2022-04-18, Repl 2022-05-02

    Description

      We have several classes which use opObservers to keep in-memory state in sync with storage state. These include sharding state, authorization, tenant migration mtabs, maybe others. These will be run during logical initial sync when the system isn't necessarily consistent, and will not be run during file copy based initial sync. Both initial syncs have special code to fix some of these after the system is consistent. We should create a mechanism (either another opObserver, or expanding/renaming the onReplicationRollback opObserver) to handle fixing these cases after initial sync generally.

      We might also consider not running the ordinary op observers during initial sync; this may require special treatment of FCV.

      Attachments

        Issue Links

          Activity

            People

              vesselina.ratcheva@mongodb.com Vesselina Ratcheva
              matthew.russotto@mongodb.com Matthew Russotto
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: