-
Type:
Bug
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Running an automated restore from a MDB 4.2.6-ent / FCV 4.2 replica set WT checkpoint snapshot into a MDB 4.4.0-rc5-ent / FCV 4.4 replica set.
During this step in the automated restore process, we get an fassert trying to start up the 4.4.0-rc5-ent non-arbiter process as a standalone:
{"t":{"$date":"2020-05-10T23:13:33.648+00:00"},"s":"W", "c":"STORAGE", "id":22347, "ctx":"initandlisten","msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."}
{"t":{"$date":"2020-05-10T23:13:33.648+00:00"},"s":"F", "c":"-", "id":23089, "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":28559,"file":"src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp","line":64}}
{"t":{"$date":"2020-05-10T23:13:33.648+00:00"},"s":"F", "c":"-", "id":23090, "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"}
{"t":{"$date":"2020-05-10T23:13:33.648+00:00"},"s":"F", "c":"CONTROL", "id":4757800, "ctx":"initandlisten","msg":"{message}","attr":{"message":"Got signal: 6 (Aborted).\n"}}
Note – this did not happen with the same test on 4.4.0-rc3 or rc4.
Found this in an automated test – attaching a potentially excessive amount of mongo logs here in case you need the historical logs.
- Logs for source rs (4.2.6):
- Logs for destination rs (4.4.0-rc5):
- depends on
-
-
- Closed
-