[SERVER-40009] Set/honour initial sync flag at the early stages of initial sync Created: 07/Mar/19  Updated: 29/Oct/23  Resolved: 25/Jun/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.0.6
Fix Version/s: 4.2.0-rc3, 4.0.13, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Josef Ahmad Assignee: Jason Chan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-29452 Handle missing featureCompatibilityVe... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2, v4.0, v3.6
Sprint: Repl 2019-06-17, Repl 2019-07-01
Participants:
Case:

 Description   

Symptoms: when the server is restarted at an early stage of the initial sync, the initial sync is unable to resume.

2019-02-27T14:58:45.498+0000 I REPL [replication-0] Starting initial sync (attempt 1 of 10)
...
2019-02-27T14:58:46.723+0000 I REPL [replication-1] CollectionCloner ns:admin.system.version finished cloning with status: CallbackCanceled: Cloner shutting down.
2019-02-27T14:58:46.724+0000 W REPL [replication-1] collection clone for 'admin.system.version' failed due to CallbackCanceled: Error cloning collection 'admin.system.version' :: caused by :: Cloner shutting down.
...
2019-02-27T14:58:49.349+0000 I CONTROL [main] ***** SERVER RESTARTED *****
...
2019-02-27T14:58:50.495+0000 F STORAGE [initandlisten] Unable to start up mongod due to missing featureCompatibilityVersion document.
2019-02-27T14:58:50.495+0000 F STORAGE [initandlisten] Please run with --repair to restore the document.
2019-02-27T14:58:50.495+0000 F - [initandlisten] Fatal Assertion 40652 at src/mongo/db/repair_database_and_check_version.cpp 581
2019-02-27T14:58:50.495+0000 F - [initandlisten]
 
***aborting after fassert() failure



 Comments   
Comment by Lawrence Tan (Inactive) [ 07/Aug/20 ]

Would it be possible to fix this for 3.6 as well? We've also been seeing flaky test that appear to be related to this in CLOUDP-68939

Comment by Githook User [ 13/Aug/19 ]

Author:

{'name': 'Jason Chan', 'username': 'jasonjhchan', 'email': 'jason.chan@10gen.com'}

Message: SERVER-40009 Honor the initial sync flag when in startup without FCV document

(cherry picked from commit c0c64c95637f8f0700ac40e89dc39c30ec6f5f41)
Branch: v4.0
https://github.com/mongodb/mongo/commit/45df410133eeb9c4fb1e9f0920a94e861f8c4585

Comment by Githook User [ 02/Jul/19 ]

Author:

{'name': 'Jason Chan', 'username': 'jasonjhchan', 'email': 'jason.chan@10gen.com'}

Message: SERVER-40009 Honor the initial sync flag when in startup without FCV document

(cherry picked from commit c0c64c95637f8f0700ac40e89dc39c30ec6f5f41)
Branch: v4.2
https://github.com/mongodb/mongo/commit/324f6029326bc01d3adcd17a2467c49887147660

Comment by Githook User [ 25/Jun/19 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@10gen.com', 'username': 'jasonjhchan'}

Message: SERVER-40009 Honor the initial sync flag when in startup without FCV document
Branch: master
https://github.com/mongodb/mongo/commit/c0c64c95637f8f0700ac40e89dc39c30ec6f5f41

Comment by Judah Schvimer [ 12/Jun/19 ]

Correct

Comment by Jason Chan [ 12/Jun/19 ]

judah.schvimer The ticket says that this ticket affects version 4.0.6. However, since this issue exists in 4.2 and master, am I correct in assuming that this change should go in master and then backported to 4.2 and 4.0?

Comment by Judah Schvimer [ 11/Mar/19 ]

cory.mintz, is this important for Atlas?

Generated at Thu Feb 08 04:53:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.