Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-69022

InitialSyncFailure error for adding a new member from replica set

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL

      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

            Assignee:
            yuan.fang@mongodb.com Yuan Fang
            Reporter:
            jason.chentj@homecredit.cn jason chen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: