[SERVER-63743] Add shardSplit commands writeConcern test support Created: 16/Feb/22 Updated: 06/Dec/22 Resolved: 31/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathis Bessa | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Serverless
|
||||||||
| Participants: | |||||||||
| Description |
|
We have added commands for the the shard split to support writeConcern . However we have a jstest that tests read and write concerns that we need to update in order to test our newly added commands. I believe the challenge here is that for our shardSplit commands we expects to have a basicServerlessTest environment which contains multiple nodes (donor and recipients) which is different than what the commands are being tested against. This was found in |
| Comments |
| Comment by Matt Broadstone [ 31/May/22 ] |
|
These tests were failing because shard split was gated by feature flag, and not supported in earlier (5.2) releases. Closing as "WONTDO" because write concern support is not meaningful for any of these commands (even though technically supported). |