[SERVER-82457] Test cases in txn_commit_optimizations_for_read_only_shards.js are not isolated from each other Created: 26/Oct/23 Updated: 22/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | cs-subteam1, sharding-nyc, sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 5 | ||||||||||||
| Story Points: | 4 | ||||||||||||
| Description |
|
Each of the test case touches different documents which in theory should not conflict with each other. However, due to |
| Comments |
| Comment by Randolph Tan [ 26/Oct/23 ] |
|
Possible directions (assuming we'll never fix I think doing any of these can potentially cause the test that already takes a long time to complete (about 11 mins in plain sharding suite) to even take longer. Perhaps we should split each failure modes into their own file so they can be parallelized (and also faster turn around for local testing). |