[SERVER-51472] Assertion during early stages of migration can cause it to get stuck Created: 09/Oct/20 Updated: 23/Oct/20 Resolved: 23/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 13 | ||||||||||||
| Description |
|
For example, if the migration caused an error while trying to write the migration coordinator document here. The cleanup code will try to call complete on the migration coordinator. This wall will get stuck in a retry loop to persist the abort decision while getting "No matching document found for query xxx on namespace config.migrationCoordinators" error over and over. |