[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: |
|
||||||||||||||||||||||||
| 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: |