[SERVER-36358] Initial replica member sync and oplog Created: 30/Jul/18 Updated: 30/Jul/18 Resolved: 30/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.2.20 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Matthew S Davis | Assignee: | Nick Brewer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
We have MongoDB 3.2 and are adding replica set members. During initial sync the connection was interupted for ~20 minutes and upon the connection being reestablished there was an error that the data was too old to catch up. The oplog size is set to the upper limit. Can you confirm that oplog is used for initial sync? Are connectivity errors during initial synch not recoverable? |
| Comments |
| Comment by Nick Brewer [ 30/Jul/18 ] |
|
matthew.s.davis62.ctr@mail.mil Yes, the oplog is used for initialsync. See the MongoDB documentation for details. That said, version 3.4 adds improved fault-tolerance for initial sync, among other benefits. If this is a recurring issue for you, I would suggest upgrading. Otherwise, you can use one of the processes outlined here. Regards, |