[SERVER-19518] mongod crashes with WriteConflictException when writing oplog on secondaries Created: 22/Jul/15  Updated: 10/Aug/15  Resolved: 10/Aug/15

Status: Closed
Project: Core Server
Component/s: Replication, WiredTiger
Affects Version/s: 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: William Richards Assignee: Scott Hernandez (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-17689 Fatal assertion during replication, a... Closed
Operating System: ALL
Steps To Reproduce:

Very difficult to reproduce, but it seems to be related to high write activity and chained replication.

Participants:

 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] 



 Comments   
Comment by Scott Hernandez (Inactive) [ 10/Aug/15 ]

William, yes this is a dup of SERVER-17689 and now available in the latest stable release of 3.0.5.

Comment by rujun [ 27/Jul/15 ]

I also encountered the same problem in 3.0.4
Under heavy load, two secondary of a 3 member replicaset went down One after another
the log is the same as this issue

Comment by Andy Schwerin [ 22/Jul/15 ]

scotthernandez, can you confirm that this is a dupe of SERVER-17689 and close the ticket, if so?

Comment by William Richards [ 22/Jul/15 ]

I would guess that the backport in SERVER-17689 addresses the issue

Generated at Thu Feb 08 03:51:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.