[SERVER-74216] Do not alter sharding's index catalog in-memory state while in recovery mode Created: 21/Feb/23  Updated: 29/Oct/23  Resolved: 24/Feb/23

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

Type: Task Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: PM-2583-Milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-03-06
Participants:

 Description   

After SERVER-69573 a new oplog entry was added to handle persisted and in-memory state for the sharding's index catalog. As part of that work the in-memory state is changed in an observer. If the node is in a recovery mode, we already have a mechanism to restore the in-memory state to a consistent one, so, executing these operations in the observer seems unnecessary.

We could use the same mechanism as the recoverable critical section to prevent doing the in-memory state changes in recovery mode.



 Comments   
Comment by Githook User [ 24/Feb/23 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-74216 Return early in the sharding index catalog observers if the node is in recovery mode
Branch: master
https://github.com/mongodb/mongo/commit/c155a7ec4b32eee6e0aa961c6d43935379120eb9

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