[SERVER-25342] Race condition in migrateBig.js between last migration cleanup and no-predicate count Created: 29/Jul/16 Updated: 13/Aug/16 Resolved: 29/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.3.10 |
| Fix Version/s: | 3.3.11 |
| Type: | Bug | 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 | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 18 (08/05/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The migrateBig.js test ensures that the count and itcount values for a collection match after all migrations have completed. However, there is a race condition in that the chunks may have been balanced, but the last chunk's migration might not have been cleaned up yet in which case the count command would find more documents that itcount. |
| Comments |
| Comment by Githook User [ 29/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |