Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
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
Attachments
Issue Links
- links to
Activity
Colin McCabe
made changes -
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Colin McCabe
made changes -
Status | Patch Available [ 10002 ] | In Progress [ 3 ] |
ASF GitHub Bot
made changes -
Remote Link | This issue links to "GitHub Pull Request #12551 (Web Link)" [ 292706 ] | This issue links to "GitHub Pull Request #12551 (Web Link)" [ 292706 ] |
ASF GitHub Bot
made changes -
Remote Link | This issue links to "GitHub Pull Request #12551 (Web Link)" [ 292706 ] | This issue links to "GitHub Pull Request #12551 (Web Link)" [ 292706 ] |
Jose Armando Garcia Sancio
made changes -
Status | Open [ 1 ] | Patch Available [ 10002 ] |
Jose Armando Garcia Sancio
made changes -
Assignee | David Arthur [ mumrah ] |
ASF GitHub Bot
made changes -
Field | Original Value | New Value |
---|---|---|
Remote Link | This issue links to "GitHub Pull Request #12551 (Web Link)" [ 292706 ] |
David Arthur
created issue -
They should contribute to the metrics. The controller needs to make sure to subtract the deferred time from the computed delay.
You can imagine a large number of delay events that couldn't be process for a while after they triggered.