[SERVER-47044] Blacklist random_moveChunk_update_shard_key.js from multi statement transaction concurrency suites Created: 23/Mar/20 Updated: 01/Apr/20 Resolved: 01/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Blake Oler | Assignee: | Blake Oler |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Multi statement transaction concurrency suites run each state function inside a transaction that's auto-retried. The random_moveChunk_update_shard_key.js workload itself attempts to update shard keys in either a retryable write or transaction. It doesn't make sense from a high level to run either update scenario in a higher level transaction. This is both unexpected and could lead to odd error scenarios (see the linked BF). We should blacklist this workload from multi statement transaction suites. |
| Comments |
| Comment by Blake Oler [ 01/Apr/20 ] |
|
This turned out to be an incorrect solution to the problem. Will not complete this ticket. |