[SERVER-21778] slave node crash: writer worker caught exception: E11000 duplicate key error Created: 05/Dec/15  Updated: 09/Jan/16  Resolved: 09/Jan/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.0.5
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: ma6174 Assignee: Ramon Fernandez Marina
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-21275 Document not found due to WT commit v... Closed
Operating System: ALL
Steps To Reproduce:

no

Participants:

 Description   

slave node crash with the log:

2015-12-05T12:20:45.640+0800 E REPL     [repl writer worker 12] writer worker caught exception:  :: caused by :: 11000 E11000 duplicate key error collection: data.rs2 index: _id_ dup key: { : "77g9ya:1_390de16e-744f-11e5-8000" } on: { ts: Timestamp 1449289245000|699, h: -2990965226155869115, v: 2, op: "u", ns: "data.rs2", o2: { _id: "77g9ya:1_390de16e-744f-11e5-8000" }, o: { _id: "77g9ya:1_390de16e-744f-11e5-8000", hash: "FuVlaMfDo7sMDmpX6hBLm-jOSSXY", fdel: 1} }
2015-12-05T12:20:45.640+0800 I -        [repl writer worker 12] Fatal Assertion 16360
2015-12-05T12:20:45.640+0800 I -        [repl writer worker 12]
 
***aborting after fassert() failure

after restart the slave node, it run normally, 3 hour passed, not crash again. the document in the slave is equal to which in master.

more information:

1. db version: 3.0.5
2. storage engine: wiredTiger
3. replset: 1master + 2slave + 2arbiter (only one slave node crash.)
4. index: only "_id" index, and never change
5. both master and the slave run more than 1 month, never upgrade, never restart, never migrate
6. one day ago adjust wiredTiger config use the command on master node(not sure if this affect the replication):

db.adminCommand({
   "setParameter": 1,
   "wiredTigerEngineRuntimeConfig": "cache_size=25G, eviction_trigger=85"
})

log:

2015-12-04T11:24:22.178+0800 I COMMAND  [conn1239841] command admin.$cmd command: setParameter { setParameter: 1.0, wiredTigerEngineRuntimeConfig: "cache_size=25G, eviction_trigger=85" } keyUpdates:0 writeConflicts:0 numYields:0 reslen:47 locks:{} 9950ms
2015-12-04T15:01:01.114+0800 I COMMAND  [conn1244358] command admin.$cmd command: setParameter { setParameter: 1.0, wiredTigerEngineRuntimeConfig: "cache_size=25G, eviction_trigger=85" } keyUpdates:0 writeConflicts:0 numYields:0 reslen:47 locks:{} 6069ms



 Comments   
Comment by Ramon Fernandez Marina [ 09/Jan/16 ]

ma6174, I'm closing this ticket as a duplicate of SERVER-21275. Please upgrade to MongoDB 3.0.8 as soon as possible. If the problem persists after the upgrade please let us know so we can investigate further.

Thanks,
Ramón.

Comment by Kelsey Schubert [ 16/Dec/15 ]

Hi ma6174,

This behavior could be caused by SERVER-21275. I would recommend upgrading to 3.0.8 as soon as possible.

Please let us know if this resolves the issue.

Thank you,
Thomas

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