Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
2.8.0-rc2
-
None
-
Fully Compatible
-
ALL
Description
Testing YCSB 50/50 against zlib against replica set seems the easiest way to reproduce this scenario.
While process is being made, one of the writing threads gets stuck on a single update for a long long time:
db.currentOp({secs_running:{$gt:50}})
|
{
|
"inprog" : [
|
{
|
"desc" : "conn28",
|
"threadId" : "0x469a820",
|
"connectionId" : 28,
|
"opid" : 3896403,
|
"active" : true,
|
"secs_running" : 408,
|
"microsecs_running" : NumberLong(408562540),
|
"op" : "update",
|
"ns" : "ycsb.usertable",
|
"query" : {
|
"_id" : "user6628373086844447656"
|
},
|
"client" : "74.86.233.3:34012",
|
"locks" : {
|
"Global" : "w",
|
"Database" : "w",
|
"local" : "w",
|
"Collection" : "w",
|
"Collection" : "w"
|
},
|
"waitingForLock" : false,
|
"lockStats" : {
|
|
|
}
|
}
|
]
|
}
|
The stack traces (will attach) seem to indicate that they are compressing large pages.
Attachments
Issue Links
- duplicates
-
SERVER-16269 WiredTiger blocks queries and updates for many seconds.
-
- Closed
-