-
Type: Bug
-
Resolution: Incomplete
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.2.6
-
Component/s: Replication
-
None
-
ALL
My MongoDB 3.2.x mmapv1 server crashed with the following stack trace. I have xxxed out some of the collection names.
The server is running on AWS and there don't appear to be any AWS or EBS issues.
2016-08-22T16:57:32.425+0000 I ACCESS [conn39] Successfully authenticated as principal admin on admin
2016-08-22T16:57:33.510+0000 F REPL [repl writer worker 10] writer worker caught exception: :: caused by :: 26 Failed to apply insert due to missing collection: { ts: Timestamp 14718850
53000|1, t: 0, h: 314096183130207904, v: 2, op: "i", ns: "xxxxxxxxx.feedback_responses", o:
} on: { ts: Timestamp 1471885053000|1, t: 0, h: 314096183130207904, v: 2, op: "i", ns: "xxxxxxxxx.feedback_responses", o:
{ _id: ObjectId('57bb2efd4543 324038840000'), AttorneyFeedback: "insufficient_time", Comments: "", AttorneyId: ObjectId('578817ef454332332c630100'), JobId: ObjectId('57b2179345433250e9790000'), ClientId: ObjectId('578818 17454332332cf00100'), ModifiedDateTime: new Date(1471885053506), CreatedDateTime: new Date(1471885053506) } }
2016-08-22T16:57:33.510+0000 I - [repl writer worker 10] Fatal Assertion 16360
2016-08-22T16:57:33.510+0000 I - [repl writer worker 10]
***aborting after fassert() failure