[SERVER-44890] MongoD RWCDefaults gets refreshed through the OpObserver Created: 02/Dec/19  Updated: 29/Oct/23  Resolved: 20/Dec/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.3.3

Type: New Feature Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-45221 Complete TODO listed in SERVER-43720 Closed
Duplicate
is duplicated by SERVER-44862 Complete TODO listed in SERVER-43126 Closed
Related
related to SERVER-45282 Unify how mongos and mongod default R... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-12-16, Sharding 2019-12-30
Participants:

 Description   

As part of this ticket, on plain replica sets, upon writing the defaults on a primary, the OpObserver (on secondaries) should update the RWCDefaults cache.



 Comments   
Comment by Githook User [ 20/Dec/19 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-44890 MongoD RWCDefaults get refreshed through the OpObserver
Branch: master
https://github.com/mongodb/mongo/commit/7d925439532fd9bbe222f679bfd2a9de99ce476d

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