[SERVER-55006] Decrease probability of spurious write conflicts in jstestfuzz Created: 05/Mar/21 Updated: 09/Mar/21 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Dan Larkin-York |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Execution Team 2021-03-22 | ||||
| Participants: | |||||
| Linked BF Score: | 25 | ||||
| Description |
|
Decrease probability of spurious write conflict in fuzz testing from 1% to ~0.1% or maybe less. Currently it looks like in concurrency suites with replication, the high probability of failure can prevent the secondary from catching up in a reasonable timeframe and then block any operation which wait for majority write concern. |
| Comments |
| Comment by Githook User [ 08/Mar/21 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |