[SERVER-61810] rename_sharded_collection.js workload needs to retry split command Created: 30/Nov/21 Updated: 29/Oct/23 Resolved: 24/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Silvia Surroca |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding EMEA 2022-05-16, Sharding EMEA 2022-05-30 | ||||||||
| Participants: | |||||||||
| Description |
|
rename_sharded_collection.js needs to retry this split because when running on concurrency_sharded_*_with_balancer suites, a concurrent migration could make the split commit fail. This is similar to what is done in this other test. |
| Comments |
| Comment by Githook User [ 20/May/22 ] |
|
Author: {'name': 'Silvia Surroca Huguet', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |