-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.8.0-rc4
-
Component/s: Storage
-
Fully Compatible
-
ALL
-
This occurs when running iibench with the WiredTiger b-tree. This does not occur with mmapv1, wiredtiger LSM, tokumx or rocksdb engines for MongoDB. While I won't rule out the client code, it looks like a WT bug to me.
It seems to occur around the time of a checkpoint stall.
The iibench client prints this on an error:
com.mongodb.WriteConcernException:
And the mongod error log has:
2015-01-04T21:49:45.625-0800 I QUERY [conn10] command iibench.$cmd command: insert
keyUpdates:0 reslen:40 12929ms
2015-01-04T21:49:45.654-0800 I QUERY [conn4] command iibench.$cmd command: insert
keyUpdates:0 reslen:40 12894ms
2015-01-04T21:49:45.658-0800 I QUERY [conn2] command iibench.$cmd command: insert
keyUpdates:0 reslen:40 12907ms
2015-01-04T21:49:53.033-0800 I WRITE [conn9] insert iibench.purchases_index query:
ninserted:0 keyUpdates:0 exception: WriteConflict code:112 4204ms
This also occurs when I use a small cache for WT which should make checkpoint stalls less of an issue.