[SERVER-64627] Need general method to handle in-memory state after initial sync Created: 17/Mar/22 Updated: 29/Oct/23 Resolved: 21/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc4, 5.0.10, 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Vesselina Ratcheva (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v6.0, v5.3, v5.0
|
||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Repl 2022-04-18, Repl 2022-05-02 | ||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
We have several classes which use opObservers to keep in-memory state in sync with storage state. These include sharding state, authorization, tenant migration mtabs, maybe others. These will be run during logical initial sync when the system isn't necessarily consistent, and will not be run during file copy based initial sync. Both initial syncs have special code to fix some of these after the system is consistent. We should create a mechanism (either another opObserver, or expanding/renaming the onReplicationRollback opObserver) to handle fixing these cases after initial sync generally. We might also consider not running the ordinary op observers during initial sync; this may require special treatment of FCV. |
| Comments |
| Comment by Githook User [ 23/May/22 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': '31660559+vessy-mongodb@users.noreply.github.com', 'username': 'vessy-mongodb'}Message: (cherry picked from commit 14e04b0acc27f7d7092eb93bf1b2666c50226d06) |
| Comment by Githook User [ 29/Apr/22 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': '31660559+vessy-mongodb@users.noreply.github.com', 'username': 'vessy-mongodb'}Message: (cherry picked from commit 14e04b0acc27f7d7092eb93bf1b2666c50226d06) |
| Comment by Githook User [ 21/Apr/22 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}Message: |
| Comment by Githook User [ 21/Apr/22 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': '31660559+vessy-mongodb@users.noreply.github.com', 'username': 'vessy-mongodb'}Message: |
| Comment by Vesselina Ratcheva (Inactive) [ 11/Apr/22 ] |
|
This ticket includes the work for |
| Comment by Kaloian Manassiev [ 18/Mar/22 ] |
|
Can we please add this to the ReplicaSetAwareService instead of the OpObserver and to include a better documentation of what exactly guarantees there are under each of the events? |