[SERVER-26418] _waitForDelete is not persisted in the migration doc Created: 30/Sep/16 Updated: 31/Oct/16 Resolved: 27/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Misha Tyulenev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2016-10-31 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
_waitForDelete is not persisted in the migration doc. So if the server running the migration is restarted its resumes the migration without this flag. Does not seem to have a real world impact, but upset continues_stepdown tests. |
| Comments |
| Comment by Githook User [ 27/Oct/16 ] |
|
Author: {u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}Message: |
| Comment by Dianna Hohensee (Inactive) [ 30/Sep/16 ] |
|
To qualify, the original moveChunk command with waitForDelete set never reaches the shard, and the moveChunk reissued after recovery without waitForDelete then arrives first and is run. If the original moveChunk made it to the shard, this would have been alright because further moveChunk commands would just wait, their waitForDelete setting ignored. |