Versions affected: recent versions of master (i.e., versions after the bump for 3.1.4)
From some preliminary bisecting, this bug seems to have been introduced since 3.1.4. It only seems to affect the WiredTiger storage engine:
m27019| 2015-06-10T15:06:40.940-0400 I INDEX [repl writer worker 15] build index on: test.foo properties: { v: 1, key: { value: 1.0 }, name: "value_1", ns: "test.foo" } m27019| 2015-06-10T15:06:40.940-0400 I INDEX [repl writer worker 15] building index using bulk method m27019| 2015-06-10T15:06:40.946-0400 I INDEX [repl writer worker 15] build index done. scanned 0 total records. 0 secs m27019| 2015-06-10T15:06:40.996-0400 E REPL [repl writer worker 10] writer worker caught exception: :: caused by :: 11000 E11000 duplicate key error collection: test.foo index: _id_ dup key: { : 8.0 } on: { ts: Timestamp 1433963200000|13, t: 0, h: -3679832681211329472, v: 2, op: "i", ns: "test.foo", o: { _id: 8.0, value: 0.0 } } m27019| 2015-06-10T15:06:40.996-0400 I - [repl writer worker 10] Fatal Assertion 16360 m27019| 2015-06-10T15:06:40.996-0400 I - [repl writer worker 10] m27019| m27019| ***aborting after fassert() failure
Versions
- is related to
-
SERVER-16444 Avoid copying data out of WT buffers during tables scans
- Closed