[SERVER-84039] write without shard key is not compatible with test suites that can cause stale config Created: 08/Dec/23 Updated: 08/Jan/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | cs-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Cluster Scalability
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 5 | ||||
| Story Points: | 5 | ||||
| Description |
|
Writes gets converted to transactions and stale config are not retryable under a transaction so they will end up getting bubbled up to the user. One example is CRUD_and_commands.js running under concurrency_sharded_with_balancer_and_auto_bootstrap |