[SERVER-42781] Race condition in migration_manager.cpp with moveChunk command Created: 12/Aug/19 Updated: 29/Oct/23 Resolved: 27/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lamont Nelson | Assignee: | Lamont Nelson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Steps To Reproduce: | see sharded_moveChunk_drop_shard_key_index.js |
||||
| Sprint: | Sharding 2019-12-02 | ||||
| Participants: | |||||
| Linked BF Score: | 4 | ||||
| Description |
|
If another moveChunk command moves the chunk concurrently. The check for the target chunk shardId here may sometimes fail and intermittently expose a "Destination shard cannot be the same as source" error to the clients. |
| Comments |
| Comment by Githook User [ 27/Nov/19 ] |
|
Author: {'email': 'lamont.nelson@mongodb.com', 'name': 'Lamont Nelson', 'username': 'lamontnelson'}Message: |
| Comment by Esha Maharishi (Inactive) [ 16/Aug/19 ] |
|
Since it's not an easy server fix and isn't particularly bad user-facing behavior, we can fix the test to ignore the specific error the shard returns. |