Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
Repl 2020-04-06, Repl 2020-04-20
-
0
Description
Similar to SERVER-26867, it would be helpful to always have hang analyzer outputs and core dumps for writeConcern timeout errors, even for assert.commandWorked.
"res" : {
|
"ok" : 0,
|
"errmsg" : "waiting for replication timed out",
|
"code" : 64,
|
"codeName" : "WriteConcernFailed",
|
"operationTime" : Timestamp(1584581044, 5),
|
"$clusterTime" : {
|
"clusterTime" : Timestamp(1584581044, 5),
|
"signature" : {
|
"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
|
"keyId" : NumberLong(0)
|
}
|
}
|
Attachments
Issue Links
- related to
-
SERVER-55159 Avoid using assert.commandWorked() to wait for writeConcern in an assert.soon() loop
-
- Closed
-
-
SERVER-47764 Trigger hang analyzer for LockTimeout errors
-
- Closed
-