[SERVER-47062] Trigger hang analyzer for writeConcern timeout errors Created: 23/Mar/20  Updated: 29/Oct/23  Resolved: 17/Apr/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-55159 Avoid using assert.commandWorked() to... Closed
related to SERVER-47764 Trigger hang analyzer for LockTimeout... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-04-06, Repl 2020-04-20
Participants:
Linked BF Score: 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)
    }
}



 Comments   
Comment by Githook User [ 17/Apr/20 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-47062: Trigger hang analyzer for writeConcern timeout errors
Branch: master
https://github.com/mongodb/mongo/commit/6bcda378bfa25ae70ac15508c171e5eeb2269958

Comment by Brooke Miller [ 24/Mar/20 ]

Based on the discussion with the STM Team, this requires adding mongorunner.runHangAnalyzer() to writeConcernErrors. Please ensure that expected failures do not trigger the hang analyzer. You can disable the hang analyzer on a case by case basis using mongorunner.runHangAnalyzer.disable().

Generated at Thu Feb 08 05:13:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.