[SERVER-28698] Use the 'chunkDataCommitted' failpoint for migration_critical_section_concurrency.js Created: 07/Apr/17 Updated: 15/Aug/17 Resolved: 10/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.5 |
| Fix Version/s: | 3.4.4, 3.5.6 |
| 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 | ||||||||
| Backport Requested: |
v3.4
|
||||||||
| Sprint: | Sharding 2017-04-17 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The current implementation of migration_critical_section_concurrency.js uses a failpoint on the MigrationDestinationManager, which however cannot be blocked for more than 30 seconds because this is the timeout for migration commit. This causes build failures on slower machines and debug builds. Instead we should be using the 'hangBeforeLeavingCriticalSection' failpoint which is on the donor shard and can be held indefinitely. |
| Comments |
| Comment by Githook User [ 11/Apr/17 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: (cherry picked from commit 61339fc6cf60938cbc83fd5b6772b10da55d4289) |
| Comment by Githook User [ 10/Apr/17 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |