[SERVER-51834] Race in moveChunk tests Created: 26/Oct/20 Updated: 29/Oct/23 Resolved: 17/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, 4.4.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Sergi Mateo Bellido |
| 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 | ||||||||
| Backport Requested: |
v4.4
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 11 | ||||||||
| Description |
|
Sequential moveChunk commands sent to a host can result in the "Unable to start new migration because this shard is currently donating chunk" The issue is raised in the moveChunk code |
| Comments |
| Comment by Githook User [ 19/Nov/20 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |
| Comment by Githook User [ 17/Nov/20 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |
| Comment by Sergi Mateo Bellido [ 16/Nov/20 ] |
|
The issue is that this code wrongly assumes that when the future is ready the objects captured in the functor were already destroyed. |
| Comment by Sergi Mateo Bellido [ 16/Nov/20 ] |
|
I managed to deterministically reproduce this issue after adding an sleep of a few seconds inside this if-stmt. |