Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-49220

failCommand with appName does not fail connection handshake command

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.4.0-rc12
    • Component/s: None
    • ALL

      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

            Assignee:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Reporter:
            shane.harvey@mongodb.com Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: