[SERVER-32062] RollbackViaRefetch should ignore NamespaceNotFound errors from sync source Created: 21/Nov/17 Updated: 06/Dec/22 Resolved: 27/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Operating System: | ALL |
| Participants: |
| Description |
|
When refetching documents and metadata, NamespaceNotFound errors should be ignored since the collection could be dropped on the sync source |
| Comments |
| Comment by Spencer Brody (Inactive) [ 27/Nov/17 ] |
|
This won't be an issue in recoverable rollback, and we have no plans to fix this for refetch-based rollback. |
| Comment by Judah Schvimer [ 21/Nov/17 ] |
|
As far as I can see in the code, we have no handling of this. It's possible the no UUID variant handles this and the UUID variant does not. They use different refetch code. |
| Comment by Spencer Brody (Inactive) [ 21/Nov/17 ] |
|
I thought we did this already? Is there a specific subset of operations where this will be a problem? |