[SERVER-46572] Remove unstable timestamp comparison from non_durable_writes_on_primary_can_reach_majority.js Created: 03/Mar/20 Updated: 29/Oct/23 Resolved: 04/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.5 |
| Type: | Bug | 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-03-09 | ||||
| Participants: | |||||
| Linked BF Score: | 19 | ||||
| Description |
|
This test check compares a secondary's durable and majority timestamps. However, there's nothing to stop the secondary from doing additional writes, for whatever internal reason, that become durable, pushing that timestamp ahead of the majority point. The check for equality is unstable. Also, improve debug-ability of non_durable_writes_on_primary_can_reach_majority.js by logging all timestamps it verifies |
| Comments |
| Comment by Githook User [ 04/Mar/20 ] |
|
Author: {'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@mongodb.com'}Message: |