-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
One of the Go driver streamable isMaster tests sets a failpoint to make isMaster requests fail with error code 91. The logs for the test execution show
{
"t":{
"$date":"2020-06-17T17:14:47.215+00:00"
},
"s":"D1",
"c":"-",
"id":23074,
"ctx":"ReplicaSetMonitor-TaskExecutor",
"msg":"User assertion ",
"attr":{
"error":"ShutdownInProgress: Failing command due to 'failCommand' failpoint",
"file":"src/mongo/client/async_client.cpp",
"line":108
}
},
{
"t":{
"$date":"2020-06-17T17:14:47.216+00:00"
},
"s":"I",
"c":"-",
"id":4333222,
"ctx":"ReplicaSetMonitor-TaskExecutor",
"msg":"RSM received failed isMaster",
"attr":{
"host":"localhost:27018",
"error":"ShutdownInProgress: Failing command due to 'failCommand' failpoint",
"replicaSet":"repl0",
"isMasterReply":"{}"
}
},
{
"t":{
"$date":"2020-06-17T17:14:47.216+00:00"
},
"s":"I",
"c":"NETWORK",
"id":4712102,
"ctx":"ReplicaSetMonitor-TaskExecutor",
"msg":"Host failed in replica set",
"attr":{
"replicaSet":"repl0",
"host":"localhost:27018",
"error":{
"code":91,
"codeName":"ShutdownInProgress",
"errmsg":"Failing command due to 'failCommand' failpoint"
},
"action":{
"dropConnections":false,
"requestImmediateCheck":false
}
}
}
One of the log lines says "RSM received failed isMaster". Does this mean that the server's internal ReplicaSetMonitor is triggering the fail point?
- depends on
-
SERVER-48985 Add logging for failCommand
-
- Closed
-
- duplicates
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-49336 Set client metadata if it is missing during failCommand
-
- Closed
-
- is related to
-
-
- Closed
-