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

Use OpStateAccumulator's to cache common state

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Storage Execution

    Description

      OpObservers independently recompute and lookup global state. Like inRecoveryMode which requires several calls to ReplicationCoordinator. The onUpdate chain computes this state at least 4 times to filter events.

       

      Currently the OpStateAccumulators are implemented post-7.0 (SERVER-76369) in a handful of methods (broadly speaking, the CRUD methods) that functionally require downstream OpObservers that observe the opTime allocated by OpObserverImpl.

       

      This ticket would extend the accumulators to be used for performance improvements on top of its existing purpose of functionally breaking dependencies.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            matt.kneiser@mongodb.com Matt Kneiser
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: