[SERVER-17044] WriteConflict in dropIndexes on WT Created: 25/Jan/15  Updated: 26/Jan/15  Resolved: 26/Jan/15

Status: Closed
Project: Core Server
Component/s: WiredTiger
Affects Version/s: 3.0.0-rc6
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Alvin Richards (Inactive) Assignee: Andy Schwerin
Resolution: Duplicate Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File daily-3.0.0-rc6-wiredTiger-m8.tgz    
Issue Links:
Duplicate
duplicates SERVER-17053 drop and dropIndexes commands should ... Closed
Operating System: ALL
Steps To Reproduce:

benchrun.py --testFilter "daily" -m 8

Participants:

 Description   

Problem

During a mongo-perf run I see the following reported. This passes on MMAPv1

Insert.EmptyCapped
1       8747.676335975568
2       13728.890263868827
Error running test [object Object]: drop failed: {
"ns" : "test5.Insert_EmptyCapped0",
"nIndexesWas" : 1,
"ok" : 0,
"errmsg" : "drop: dropIndexes for collection failed. cause: WriteConflict. See http://dochub.mongodb.org/core/data-recovery",
"code" : 1
}

The logs seem to indicate the the drop was executed, but then the following insert (in the timeline) tripped this

2015-01-25T10:25:59.859-0800 I COMMAND  [conn3] CMD: drop test0.Insert_EmptyCapped0
2015-01-25T10:25:59.862-0800 I COMMAND  [conn3] CMD: drop test1.Insert_EmptyCapped0
2015-01-25T10:25:59.865-0800 I COMMAND  [conn3] CMD: drop test2.Insert_EmptyCapped0
2015-01-25T10:25:59.867-0800 I COMMAND  [conn3] CMD: drop test3.Insert_EmptyCapped0
2015-01-25T10:25:59.869-0800 I COMMAND  [conn3] CMD: drop test4.Insert_EmptyCapped0
2015-01-25T10:25:59.871-0800 I COMMAND  [conn3] CMD: drop test5.Insert_EmptyCapped0
2015-01-25T10:25:59.874-0800 I COMMAND  [conn3] CMD: drop test6.Insert_EmptyCapped0
2015-01-25T10:25:59.876-0800 I COMMAND  [conn3] CMD: drop test7.Insert_EmptyCapped0
2015-01-25T10:25:59.878-0800 I COMMAND  [conn3] CMD: drop test0.Insert_EmptyCapped0
2015-01-25T10:25:59.878-0800 I COMMAND  [conn3] CMD: drop test1.Insert_EmptyCapped0
2015-01-25T10:25:59.878-0800 I COMMAND  [conn3] CMD: drop test2.Insert_EmptyCapped0
2015-01-25T10:25:59.879-0800 I COMMAND  [conn3] CMD: drop test3.Insert_EmptyCapped0
2015-01-25T10:25:59.879-0800 I COMMAND  [conn3] CMD: drop test4.Insert_EmptyCapped0
2015-01-25T10:25:59.879-0800 I COMMAND  [conn3] CMD: drop test5.Insert_EmptyCapped0
2015-01-25T10:25:59.879-0800 I COMMAND  [conn3] CMD: drop test6.Insert_EmptyCapped0
2015-01-25T10:25:59.880-0800 I COMMAND  [conn3] CMD: drop test7.Insert_EmptyCapped0
2015-01-25T10:25:59.880-0800 I COMMAND  [conn3] CMD: drop test0.Insert_EmptyCapped0
2015-01-25T10:25:59.882-0800 I COMMAND  [conn3] CMD: drop test1.Insert_EmptyCapped0
2015-01-25T10:25:59.884-0800 I COMMAND  [conn3] CMD: drop test2.Insert_EmptyCapped0
2015-01-25T10:25:59.885-0800 I COMMAND  [conn3] CMD: drop test3.Insert_EmptyCapped0
2015-01-25T10:25:59.887-0800 I COMMAND  [conn3] CMD: drop test4.Insert_EmptyCapped0
2015-01-25T10:25:59.889-0800 I COMMAND  [conn3] CMD: drop test5.Insert_EmptyCapped0
2015-01-25T10:25:59.891-0800 I COMMAND  [conn3] CMD: drop test6.Insert_EmptyCapped0
2015-01-25T10:25:59.892-0800 I COMMAND  [conn3] CMD: drop test7.Insert_EmptyCapped0
2015-01-25T10:25:59.895-0800 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:46742 #5936 (2 connections now open)
2015-01-25T10:25:59.895-0800 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:46743 #5937 (3 connections now open)
2015-01-25T10:25:59.895-0800 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:46744 #5938 (4 connections now open)
2015-01-25T10:25:59.895-0800 I NETWORK  [conn5936] end connection 127.0.0.1:46742 (3 connections now open)
2015-01-25T10:26:02.562-0800 I WRITE    [conn5938] insert test1.Insert_EmptyCapped0 ninserted:1 keyUpdates:0 writeConflicts:0 numYields:0 111ms
2015-01-25T10:26:02.562-0800 I COMMAND  [conn5938] command test1.$cmd command: insert { insert: "Insert_EmptyCapped0", documents: [ {} ] } ntoreturn:1 keyUpdates:0 writeConflicts:0 numYields:0 reslen:40 111ms
2015-01-25T10:26:04.896-0800 I NETWORK  [conn5937] end connection 127.0.0.1:46743 (2 connections now open)
2015-01-25T10:26:04.896-0800 I NETWORK  [conn5938] end connection 127.0.0.1:46744 (1 connection now open)
2015-01-25T10:26:04.896-0800 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:46745 #5939 (2 connections now open)
2015-01-25T10:26:04.896-0800 I NETWORK  [conn5939] end connection 127.0.0.1:46745 (1 connection now open)
2015-01-25T10:26:04.897-0800 I COMMAND  [conn3] CMD: drop test0.Insert_EmptyCapped0
2015-01-25T10:26:04.902-0800 I COMMAND  [conn3] CMD: drop test1.Insert_EmptyCapped0
2015-01-25T10:26:04.906-0800 I COMMAND  [conn3] CMD: drop test2.Insert_EmptyCapped0
2015-01-25T10:26:04.910-0800 I COMMAND  [conn3] CMD: drop test3.Insert_EmptyCapped0
2015-01-25T10:26:04.913-0800 I COMMAND  [conn3] CMD: drop test4.Insert_EmptyCapped0
2015-01-25T10:26:04.917-0800 I COMMAND  [conn3] CMD: drop test5.Insert_EmptyCapped0
2015-01-25T10:26:44.455-0800 W STORAGE  [conn3] drop: dropIndexes for collection failed. cause: WriteConflict. See http://dochub.mongodb.org/core/data-recovery
2015-01-25T10:26:44.455-0800 I COMMAND  [conn3] command test5.$cmd command: drop { drop: "Insert_EmptyCapped0" } keyUpdates:0 writeConflicts:0 numYields:0 reslen:222 39538ms
2015-01-25T10:26:44.461-0800 I NETWORK  [conn3] end connection 127.0.0.1:40736 (0 connections now open)



 Comments   
Comment by Andy Schwerin [ 26/Jan/15 ]

This is a duplicate, I'll find the matching ticket tomorrow.

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