ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aravindan Vijayan" <avija...@hortonworks.com>
Subject Review Request 39693: Flume metrics do not match up with data being processed by storm
Date Tue, 27 Oct 2015 18:03:01 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39693/
-----------------------------------------------------------

Review request for Ambari, Dmytro Sen, Sumit Mohanty, and Sid Wagle.


Bugs: AMBARI-13585
    https://issues.apache.org/jira/browse/AMBARI-13585


Repository: ambari


Description
-------

Problem
Flume Metrics shown in the flume summary page of Ambari have very small values when correlated
with the events being generated by the flume agents.

Bug
AMS handles flume metrics in a special way since they are "rate" metrics. While trying to
calculate the "per second" metric value, the code calculates the "per millisecond" value instead.

Fix
Changed calculation logic to "per second".


Diffs
-----

  ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java
21f193f 

Diff: https://reviews.apache.org/r/39693/diff/


Testing
-------

Maunal Testing by creating flume agents.

mvn clean test on ambari-metrics.


Thanks,

Aravindan Vijayan


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message