[SERVER-69022] InitialSyncFailure error for adding a new member from replica set Created: 21/Aug/22  Updated: 26/Aug/22  Resolved: 26/Aug/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: jason chen Assignee: Yuan Fang
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Hi Mongo community, 

Recently, am adding a new member from mongo replica set (Total size 500GB+).

There is an error : 

======================================================

2022-08-21T00:45:12.381+0800 W REPL     [repl writer worker 5] database 'DB_TAE' (4 of 6) clone failed due to InitialSyncFailure: Failed to clone 1 collection(s) in 'DB_TAE' from 10.25.14.185:27067
2022-08-21T00:45:12.381+0800 I REPL     [repl writer worker 5] Finished cloning data: InitialSyncFailure: Failed to clone 1 collection(s) in 'DB_TAE' from 10.25.14.185:27067. Beginning oplog replay.
2022-08-21T00:45:12.381+0800 I REPL     [replication-557] Finished fetching oplog during initial sync: CallbackCanceled: error in fetcher batch callback: oplog fetcher is shutting down. Last fetched optime and hash: { ts: Timestamp(1661013931, 4), t: 25 }[-9216962259998492407]
2022-08-21T00:45:12.381+0800 I REPL     [replication-557] Initial sync attempt finishing up.

...

...

2022-08-21T00:45:13.577+0800 I STORAGE  [replication-556] dropAllDatabasesExceptLocal 5

===================================================

Then the  initial sync will be started from the beginning again.  All the cloned the database were removed and started from zero. 

It can be reproduced.

PROD ENV:  

Mongo version :4.0.

OS  version:  Red Hat Enterprise Linux Server release 7.8 (Maipo)

Thanks
Jason



 Comments   
Comment by Yuan Fang [ 26/Aug/22 ]

Hi Jason,

We'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums. Before posting yours, you may want to search for existing posts that may relates to the issue you reported.  Checkout this one: #why the new replication member not continuing the replication

Please be aware that MongoDB version 4.0 reached the end of life in April 2022 and is no longer supported. We strongly suggest you upgrade to MongoDB v4.2+. If the error still occurs and the discussion on the forums leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project.

Generated at Thu Feb 08 06:12:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.