-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: 4.4.0-rc12
-
Component/s: None
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
It look like after the changes in SERVER-48985 (4.4.0-rc11-9-gee10647) the behavior of failCommand has changed slightly. It's no longer possible to fail the initial connection handshake and specify an appName filter. For example, the following failpoint on 4.4.0-rc11 will trigger on the connection handshake, now it only triggers on subsequent isMaster commands:
{
'configureFailPoint': 'failCommand',
'mode': {'times': 2},
'data': {
'failCommands': ['isMaster'],
'closeConnection': False,
'errorCode': 91,
'appName': 'failHandshakeTest',
},
}
Is this the same issue described in SERVER-48985 and SERVER-49157?
CC: ben.caimano
- depends on
-
SERVER-49336 Set client metadata if it is missing during failCommand
-
- Closed
-
- duplicates
-
-
- Closed
-
- is caused by
-
SERVER-48985 Add logging for failCommand
-
- Closed
-
- is duplicated by
-
-
- Closed
-