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

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

    XMLWordPrintableJSON

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

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-64601 Shard server mongod initialization is not run after File Copy Based Initial Sync

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          Task - A task that needs to be done. SERVER-65251 FCBIS doesn't call to the onInitialSyncComplete ReplicaSetAwareService hook

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-64433 A new topology time could be gossiped without being majority committed

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-64601 Shard server mongod initialization is not run after File Copy Based Initial Sync

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-66082 Ensure that cluster parameters are applied in-memory during file-copy based initial sync

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

          Task - A task that needs to be done. SERVER-69017 Clarify interface for initializing in-memory state

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-64628 More testing of adding nodes to sharded sets

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: