[SERVER-51528] Make secondary import dryRun application async Created: 13/Oct/20 Updated: 29/Oct/23 Resolved: 15/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2020-10-19 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 2 | ||||||||
| Description |
|
During the dry run, when we’re trying to drop the ident from the storage engine, it’s possible that we can get EBUSY if there’s a concurrent checkpoint running. A consequence of this is that it blocks replication today. Making the dry run application run asynchronously resolves this issue. |
| Comments |
| Comment by Githook User [ 14/Oct/20 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |