[SERVER-63708] Ensure that TTL indexes work correctly with user write blocking Created: 15/Feb/22  Updated: 29/Oct/23  Resolved: 15/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

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

Issue Links:
Depends
depends on SERVER-63521 Reject user writes when user write bl... Closed
depends on SERVER-63702 Set in-memory user write blocking sta... Closed
Backwards Compatibility: Fully Compatible
Sprint: Security 2022-03-21
Participants:

 Description   

When user write blocking is enabled, we must not perform TTL monitoring/reaping on user data. However, reaping of system and internal collections must work normally.

There is no need to synchronize activation of user write blocking mode with the TTL monitor thread.

We should ensure that the TTL monitor thread, and the operations it issues, are affected by write blocking mode. We should write JS integration tests to validate that TTL indexes are disabled on user collections, and functioning on administrative collections.

A collection needs to be on one of the following databases to be considered administrative:

  • admin
  • local
  • config

system. collections should not necessarily be considered administrative.



 Comments   
Comment by Githook User [ 15/Mar/22 ]

Author:

{'name': 'Spencer Jackson', 'email': 'spencer.jackson@mongodb.com', 'username': 'spencerjackson'}

Message: SERVER-63708 Ensure that TTL indexes work correctly with user write blocking
Branch: master
https://github.com/mongodb/mongo/commit/054160f7e2232f398ec23e90fb83aa81cd2861d0

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