[SERVER-11638] Primary crashes because of duplicate key error Created: 08/Nov/13 Updated: 16/Nov/21 Resolved: 30/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.5 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Sergey Novgorodsky | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | crash, replicaset | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux on EC2 |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
We run two replica sets, three nodes in each set (mongo v2.4.5) Wed Nov 6 20:40:30.380 [repl writer worker 6] ERROR: writer worker caught exception: E11000 duplicate key error index: markover.reply.$pollID_1_replyID_1 dup key: { : null, : null } on: { ts: Timestamp 1383770430000|8, h: 4197632611217932450, v: 2, op: "u", ns: "markover.reply", o2: { _id: ObjectId('51eebff86ea332056f00034b') }, o: { $set: { uncertain: false, vote: "testvote" } } } ***aborting after fassert() failure Wed Nov 6 20:40:30.427 Got signal: 6 (Aborted). Wed Nov 6 20:40:30.438 Backtrace: My understanding is that a duplicate key error shouldn't cause a fatal crash. Thanks |
| Comments |
| Comment by Ramon Fernandez Marina [ 30/May/14 ] |
|
snovgorodsky please see |