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

Set in-memory user write blocking state in mongod command

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.3.0-rc1
    • None
    • None
    • Fully Compatible
    • Security 2022-02-21

    Description

      In SERVER-63451, we created a TypedCommand which would eventually control the user write blocking state for the cluster.

      In SERVER-63611, we defined the in-memory state which track whether user write blocking was active, but we did not implement the replication or sharding machinery which would drive it.

      For our short-term implementation and testing requirements, we should wire the mongod command to directly control the in-memory state, without the propagation logic.

      This will allow us to integrate all of our logic, and test standalones and replicaset primaries, as well as develop the first draft of our integration tests. Note that nodes will not be able to recover the in-memory state after a shutdown or a failover.

      Attachments

        Issue Links

          Activity

            People

              gabriel.marks@mongodb.com Gabriel Marks
              spencer.jackson@mongodb.com Spencer Jackson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: