Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-14178

NoOpRecord incorrectly causes high controller queue time metric

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 3.3.0
    • controller, kraft, metrics
    • None

    Description

      When a deferred event is added to the queue in ControllerQuorum, we include the total time it sat in the queue as part of the "EventQueueTimeMs" metric in QuorumControllerMetrics.

      With the introduction of NoOpRecords, the p99 value for this metric is equal to the frequency that we schedule the no-op records. E.g., if no-op records are scheduled every 5 seconds, we will see p99 EventQueueTimeMs of 5 seconds.

      This makes it difficult (impossible) to see if there is some delay in the event processing on the controller.

      Attachments

        Issue Links

          Activity

            People

              mumrah David Arthur
              mumrah David Arthur
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: