Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Duplicate
-
3.2.1
-
None
-
None
-
ALL
Description
Our replica contains a primary, secondary and arbiter. Data is backed up periodically from the secondary using the recommended method (fsync lock & snapshotting). When we create a new member based on the backup - and add it to the set - it will not sync, showing this - endlessly without doing anything:
2016-02-01T05:33:38.739+0000 I REPL [ReplicationExecutor] syncing from: in.db2m2.mydomain.com:27017
|
2016-02-01T05:33:43.812+0000 I REPL [ReplicationExecutor] syncing from: in.db2m2.mydomain.com:27017
|
2016-02-01T05:33:48.885+0000 I REPL [ReplicationExecutor] syncing from: in.db2m2.mydomain.com:27017
|
This happen for very recent backups (a few minutes old). Note that the data dir contains data which is identical to our secondary node, which does sync correctly, even if stopped.
This worked for us in 3.0.
Happens with protocol version 0 and 1.
A log with verbose level 5 is attached. We can easily reproduce it.
Please advise, the only way for us to add a member is to have a full initial sync which is unrealistic (our DB size is 8TB).
Attachments
Issue Links
- duplicates
-
SERVER-22456 The oplog find query timeout is too low
-
- Closed
-