[SERVER-26089] Incorrect assertion in the migration commit code Created: 13/Sep/16 Updated: 19/Nov/16 Resolved: 15/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.14 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2016-09-19 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The post-error refresh collection version assertions in the migration commit code are incorrect because they fail to account for parallel migrations. We should remove them. In addition, we should enable the bulk_shard_insert.js test in the continuous stepdown suite since it is very useful since it does stepdowns while chunks are migrated as result of top chunk auto splits. |
| Comments |
| Comment by Githook User [ 15/Sep/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: Enables the bulk_shard_insert.js test in the continuous stepdown suite and |