[SERVER-26232] MigrationManager::finishRecovery will attempt and fail to remove migration documents, which is good, but it shouldn't be trying Created: 21/Sep/16 Updated: 06/Dec/22 Resolved: 08/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Sprint: | Sharding 2017-01-02 |
| Participants: |
| Description |
|
This isn't causing any issues, because when the MigrationManager is interrupted the write will fail. But it shouldn't do it. When the finishRecovery waits for the moveChunk commands to finish here, it should check the error code and run ScopedMigrationRequest::keepDocumentOnDestruct. |