[SERVER-76847] Consider removing fuzzing from *concurrency_sharded_replication test suites Created: 04/May/23 Updated: 09/May/23 Resolved: 09/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Participants: | |||||
| Linked BF Score: | 150 | ||||
| Description |
|
The *concurrency_sharded_replication test suites often have issues wherein operations time out because of the highly loaded system. It's unclear that fuzzing on top of this is helpful, since changing the server parameters can easily increase or decrease load and cause timeout swings. |
| Comments |
| Comment by Gregory Wlodarek [ 09/May/23 ] |
|
If we start seeing more noise from this suite we'll re-open this.
|