[SERVER-65681] set_cluster_parameter_replset.js should be tagged "requires_persistence" Created: 14/Apr/22 Updated: 29/Oct/23 Resolved: 14/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc1, 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | David Storch |
| 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
|
||||||||
| Sprint: | QE 2022-04-18 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 161 | ||||||||
| Description |
|
This test restarts all of the nodes in the replica set around the same time. This means that all three nodes can lose their data when running on the inMemory storage engine. Depending on the timing, all three nodes can end up trying to initial sync from one another. Eventually they fassert() because they cannot find a sync source. This test should be tagged "requires_persistence" to prevent it from running with the inMemory storage engine. Thanks to judah.schvimer@mongodb.com for helping me understand the problem! |
| Comments |
| Comment by Githook User [ 14/Apr/22 ] |
|
Author: {'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}Message: (cherry picked from commit fb9cf156cfa629dedef54fba47ea5055732356eb) |
| Comment by Githook User [ 14/Apr/22 ] |
|
Author: {'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}Message: |