[SERVER-41386] Create a JS test that ensures non-durable writes can replicate but are not counted for majority write concern Created: 30/May/19 Updated: 29/Oct/23 Resolved: 26/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (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 | ||||||||||||||||||||
| Sprint: | Execution Team 2020-01-13, Execution Team 2020-01-27, Execution Team 2020-02-10, Execution Team 2020-02-24, Execution Team 2020-03-09 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 25 | ||||||||||||||||||||
| Description |
|
Write a test that stops/delays journal flushing on the primary in a 3-node set, and then check that the majority point can still move forward after writes occur. Then, shut down a secondary so that the primary must be part of the majority set, and see that the majority point does not move forward after writes occur. This test will prove that we are using the correct logic to calculate a majority, using "durable" timestamps. |
| Comments |
| Comment by Githook User [ 27/Feb/20 ] |
|
Author: {'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@mongodb.com'}Message:
create mode 100644 jstests/noPassthrough/non_durable_writes_on_primary_can_reach_majority.js |