[SERVER-66082] Ensure that cluster parameters are applied in-memory during file-copy based initial sync Created: 29/Apr/22  Updated: 29/Oct/23  Resolved: 13/May/22

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

Type: Bug Priority: Major - P3
Reporter: Varun Ravichandran Assignee: Varun Ravichandran
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-64627 Need general method to handle in-memo... Closed
is related to SERVER-64601 Shard server mongod initialization is... Closed
is related to SERVER-69015 Add cluster parameter consistency che... Blocked
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.0
Sprint: Security 2022-05-16
Participants:

 Description   

During logical initial sync, oplog events are applied on the new node and trigger OpObserver events as they are applied, which ensures that the updates are propagated to in-memory threads that consume these values. File-copy based initial sync, however, does not trigger the OpObserver hooks. This means that replica set nodes that are added via file-copy based initial sync will not have the correct values in-memory at the end of initial sync.

We should adopt an approach similar to SERVER-64601 in order to ensure that cluster parameters are properly initialized in-memory when file-copy based initial sync is used.



 Comments   
Comment by Githook User [ 16/May/22 ]

Author:

{'name': 'Varun Ravichandran', 'email': 'varun.ravichandran@mongodb.com', 'username': 'varunravi98'}

Message: SERVER-66082: Propagate cluster server parameters to new nodes during file-copy based initial sync

(cherry picked from commit 33ced84ad3537acb5a70907b6febb34adbcfbbcc)
Branch: v6.0
https://github.com/mongodb/mongo/commit/4ad4646e089410bee0926806d10f809baab9fbe9

Comment by Githook User [ 16/May/22 ]

Author:

{'name': 'Varun Ravichandran', 'email': 'varun.ravichandran@mongodb.com', 'username': 'varunravi98'}

Message: SERVER-66082: Propagate cluster server parameters to new nodes during file-copy based initial sync

(cherry picked from commit 9f13785685a93c8ce4adfc563c34021b333c81ef)
Branch: v6.0
https://github.com/10gen/mongo-enterprise-modules/commit/3fffc3cd5c76abeb4bb54443d3fb1d4ce7cb3c6e

Comment by Githook User [ 13/May/22 ]

Author:

{'name': 'Varun Ravichandran', 'email': 'varun.ravichandran@mongodb.com', 'username': 'varunravi98'}

Message: SERVER-66082: Propagate cluster server parameters to new nodes during file-copy based initial sync
Branch: master
https://github.com/mongodb/mongo/commit/33ced84ad3537acb5a70907b6febb34adbcfbbcc

Comment by Githook User [ 13/May/22 ]

Author:

{'name': 'Varun Ravichandran', 'email': 'varun.ravichandran@mongodb.com', 'username': 'varunravi98'}

Message: SERVER-66082: Propagate cluster server parameters to new nodes during file-copy based initial sync
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/9f13785685a93c8ce4adfc563c34021b333c81ef

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