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

ReplicaSetMonitor hitting failpoint set during drivers test

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

      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?

            Assignee:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Reporter:
            divjot.arora@mongodb.com Divjot Arora (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: