Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Duplicate
-
3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4
-
None
-
None
-
ALL
-
Description
Under heavy load, a secondary of a 3 member replicaset went down with the following final lines in the log:
2015-07-21T08:40:44.541-0400 I NETWORK [initandlisten] connection accepted from (secondary) #14060 (219 connections now open)
|
2015-07-21T08:40:44.567-0400 I ACCESS [conn14060] Successfully authenticated as principal __system on local
|
2015-07-21T08:40:46.434-0400 I REPL [rsSync] WriteConflictException while writing oplog, retrying.
|
2015-07-21T08:40:46.475-0400 F REPL [rsSync] replication oplog stream went back in time. previous timestamp: 55ae3dd4:28 newest timestamp: 55ae3d60:c. Op being applied: { ts: Timestamp 1437482336000|12, h: 5080621651469059829, v: 2, op: "u", ns: "db.coll", o2: { _id: ObjectId('55ad20d2479b1e68cb2f3011') }, o: { $set: { xxx.16: { _id: ObjectId('55ad2818479b1e68cb2f36a7'), xxx: [ { C: "Cu", N: "F" } ] } } } }
|
2015-07-21T08:40:46.477-0400 I - [rsSync] Fatal Assertion 18905
|
2015-07-21T08:40:46.477-0400 I - [rsSync]
|
Attachments
Issue Links
- duplicates
-
-
- Closed
-