ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18289) Invalid negative values for some AMS metrics
Date Thu, 15 Sep 2016 00:40:20 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-18289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491910#comment-15491910
] 

Hudson commented on AMBARI-18289:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5673 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5673/])
AMBARI-18289 : Invalid negative values for some AMS metrics. (avijayan) (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9455b52dd3126248ccea0d077d5da4512f4e2f21])
* (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/templates/metric_monitor.ini.j2
* (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-env.xml
* (edit) ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/config_reader.py
* (edit) ambari-metrics/ambari-metrics-host-monitoring/conf/unix/metric_monitor.ini
* (edit) ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/host_info.py
* (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py


> Invalid negative values for some AMS metrics
> --------------------------------------------
>
>                 Key: AMBARI-18289
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18289
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.4.0
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18289-2.patch
>
>
> PROBLEM
> Negative values are being reported for IOPS in the "system servers" dashboard
> BUG
> This was a dockerized environment. Negative rate values were seen because read/write
counters were dropping below the previous values at random times. On further investigation,
it revealed that this was due to the docker volume groups present on the host. It is expected
of docker containers to add/remove the volume groups during the lifecyle of a container. So,
when a volume group goes away, the read/write counters do not contribute to the total counter
values, thus making the value go below the last seen value.
> FIX
> Have a provision to discard such "special" disk partitions through a skip pattern. Individual
disk counter metrics can be used to get disk specific counter values. If skipped, they will
not contribute to the global counter metric.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message