[
https://issues.apache.org/jira/browse/HELIX-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673669#comment-16673669
]
Hudson commented on HELIX-785:
------------------------------
FAILURE: Integrated in Jenkins build helix #1569 (See
[https://builds.apache.org/job/helix/1569/])
[HELIX-785] Record helix latency instead of user latency in top state (hrzhang:
rev ccf263c9110fa5af54f1c1cabd8b5a2af64d473e)
* (edit)
helix-core/src/main/java/org/apache/helix/monitoring/mbeans/ClusterStatusMonitor.java
* (edit)
helix-core/src/test/java/org/apache/helix/monitoring/mbeans/TestTopStateHandoffMetrics.java
* (edit) helix-core/src/test/resources/TestTopStateHandoffMetrics.json
* (edit)
helix-core/src/main/java/org/apache/helix/controller/stages/TopStateHandoffReportStage.java
* (edit)
helix-core/src/main/java/org/apache/helix/monitoring/mbeans/ResourceMonitor.java
> Report helix latency instead of user latency during top state handoff
> ---------------------------------------------------------------------
>
> Key: HELIX-785
> URL: https://issues.apache.org/jira/browse/HELIX-785
> Project: Apache Helix
> Issue Type: Task
> Reporter: Harry Zhang
> Assignee: Harry Zhang
> Priority: Major
>
> Currently we are reporting top state handoff user latency, but we should
> report Helix latency instead. user should have their way of monitoring their
> own state transitions.
> AC:
> 1. Implement reporting Helix latency for top state handoff and test it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
