[SERVER-63702] Set in-memory user write blocking state in mongod command Created: 15/Feb/22  Updated: 29/Oct/23  Resolved: 17/Feb/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0-rc1

Type: Task Priority: Major - P3
Reporter: Spencer Jackson Assignee: Gabriel Marks
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-63451 Define a TypedCommand for setUserWrit... Closed
depends on SERVER-63611 Create in-memory state holder for use... Closed
is depended on by SERVER-63457 Expose write blocking state in server... Closed
is depended on by SERVER-63708 Ensure that TTL indexes work correctl... Closed
Backwards Compatibility: Fully Compatible
Sprint: Security 2022-02-21
Participants:

 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.



 Comments   
Comment by Githook User [ 17/Feb/22 ]

Author:

{'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}

Message: SERVER-63702 Wire setUserWriteBlockMode to in-memory state
Branch: master
https://github.com/mongodb/mongo/commit/bd09f35f9f13d6ca5f58c0f292911c0af32fdecf

Generated at Thu Feb 08 05:58:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.