Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
4.0.6
-
None
-
Fully Compatible
-
ALL
-
v4.2, v4.0, v3.6
-
Repl 2019-06-17, Repl 2019-07-01
-
(copied to CRM)
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
|
Attachments
Issue Links
- related to
-
SERVER-29452 Handle missing featureCompatibilityVersion document during startup
-
- Closed
-