[SERVER-38707] Exhaustively test significant writeConcern and commitQuorum combination scenarios with cross-replica set index builds Created: 19/Dec/18 Updated: 27/Oct/23 Resolved: 07/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
Check that indexes are present or not present as expected. Fail points might be necessary for non-deterministic testing. This is to make sure there are no writeConcern errors as a result of the asynchronously running index builds relative to a createIndexes command request, along with the joining existing index builds functionality with different callers obeying different writeConcern for the same build – need to make sure that is tested, too. |