-
Type: Task
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Serverless
Currently I am not clear on how we handle errors on recipient secondaries while copying & importing donor files.
1) Say copying a particular donor file failed on recipient secondary, how do we prevent recipient secondaries from copying subsequent donor files? The current design is that for each entry in the backup cursor response (donor files to be imported list), we generate an oplog entry and an op observer for that entry would trigger the copying of that particular file.
2) Does recipient secondary need to inform recipient primary to abort merge?
- depends on
-
SERVER-61144 Finish importing donated collections on secondaries
- Closed
- duplicates
-
SERVER-63390 Abort merge on error from OpObserver or FileImporter
- Closed