-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: 4.4.9
-
Component/s: None
-
Labels:
-
Environment:AWS EC2 Linux2 Graviton
-
Storage - Ra 2021-10-04
-
8
Previously running on version 4.4.8 in a three node repl set and experienced DuplicateKey bug which crashed mongodb and required resync on secondary node.
Issue tracked here: https://jira.mongodb.org/browse/WT-7984
Upgraded all nodes to version 4.4.9 which was supposed to resolve this, however, just hit the same bug again.
{"t":{"$date":"2021-09-30T03:32:53.024+00:00"},"s":"F", "c":"-", "id":23095, "ctx":"OplogApplier-0","msg":"Fatal assertion","attr":{"msgid":34437,"error":"DuplicateKey{ keyPattern: { _id: 1 }, keyValue: { _id: \"bb62e2b7dd714f89b9b3abceba139f23\" } }: E11000 duplicate key error collection: Session.Session index: _id_ dup key: { _id: \"bb62e2b7dd714f89b9b3abceba139f23\" }","file":"src/mongo/db/repl/oplog_applier_impl.cpp","line":510}}
{"t":{"$date":"2021-09-30T03:32:53.024+00:00"},"s":"F", "c":"-", "id":23096, "ctx":"OplogApplier-0","msg":"\n\n***aborting after fassert() failure\n\n"}
