[SERVER-71919] Clean up orphaned collections on recipient after movePrimary failure Created: 07/Dec/22 Updated: 29/Oct/23 Resolved: 10/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23 |
| Participants: |
| Description |
|
In case of a failure of a movePrimary operation, dirty data (partially or fully cloned) could remain on the recipient node, causing a persistent failure of any subsequent movePrimary operation attempts (NamespaceExists error). In order to recover, a manual drop operation of this dirty data is required on the recipient node. |
| Comments |
| Comment by Githook User [ 10/Jan/23 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |