[SERVER-31014] Fail initial sync on first collection cloner failure Created: 08/Sep/17 Updated: 30/Oct/23 Resolved: 04/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Vesselina Ratcheva (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2018-08-13, Repl 2018-08-27, Repl 2018-09-10, Repl 2018-09-24, Repl 2018-10-08 |
| Participants: |
| Description |
|
If a collection clone fails, we continue cloning the rest of the database: https://github.com/mongodb/mongo/blob/d4a9df74058d91f0adf977365589578dca1c1ff1/src/mongo/db/repl/database_cloner.cpp#L413-L414. This is from a previous design and is no longer useful. |
| Comments |
| Comment by Githook User [ 04/Oct/18 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}Message: |