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

Log when flow control is engaged and disengaged

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Do
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 4.4.0
    • Component/s: Logging, Performance
    • None
    • Storage Execution

      The engagement determination will be based on whether the targetRateLimit (as seen in FTDC) is throttled to be less than the maximum. Every time the targetRateLimit transitions from "max" to "less than max", the "flow control engaged" message will be logged, and every time the targetRateLimit transitions from "less than max" to "max", the "flow control disengaged" message will be logged. Note that depending on the workload, these messages could be very noisy, so let's not introduce them at the default log level, but instead at debug log level 1.

      Original description:

      This is a feature request. The mongod error log has messages to indicate when flow control is engaged. This request is to log when it is disengaged. That makes it easier to see when flow control might explain performance problems.

      An example when it is engaged is:

      {"t":{"$date":"2020-09-03T20:18:35.656+00:00"},"s":"W",  "c":"STORAGE",  "id":22225,   "ctx":"FlowControlRefresher","msg":"Flow control is engaged and the sustainer point is not moving. Please check the health of all secondaries."}

            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            mark.callaghan@mongodb.com Mark Callaghan (Inactive)
            0 Vote for this issue
            7 Start watching this issue