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

`Set failpoint` server log doesn't contain configureFailPoint mode.times value.

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Logging
    • Service Arch

      When I configure the below failpoint on driver side:

       

      {
          "configureFailPoint": "failCommand",
          "mode": {
              "times": 1   // pay attention here
          },
          "data": {
              "failCommands": ["ping"],
              "appName": "app",
              "blockConnection": true,
              "blockTimeMS": 1000
          }
      }

      with times : 1, I would expect this value in the server log too, but it doesn't happen.

       

      The actual log content is:

       

      {
          "t": {
              "$date": "2020-09-16T02:38:33.175+03:00"
          },
          "s": "W",
          "c": "CONTROL",
          "id": 23829,
          "ctx": "conn3",
          "msg": "Set failpoint",
          "attr": {
              "failPointName": "failCommand",
              "failPoint": {
                  "mode": 3,
                  "data": {
                      "failCommands": ["ping"],
                      "appName": "app",
                      "blockConnection": true,
                      "blockTimeMS": 1000
                  },
                  "timesEntered": 0
              }
          }
      } 

      Is it a expected?

       

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            dmitry.lukyanov@mongodb.com Dmitry Lukyanov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: