[
https://issues.apache.org/jira/browse/AMBARI-18289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15511859#comment-15511859
]
Ponder-Hoover commented on AMBARI-18289:
----------------------------------------
build Ambari 2.4.1 source meet
:ambari-metrics-host-monitoring/target/psutipsutil/_psutil_linux.c:12:20:
error: Python.h: No such file or directory
Pre-Configured Development Environment:
Centos6.5,
Python 2.6.6
Sun JDK1.7.0_80
NodeJS v0.10.44
Brunch 1.7.20
Build and install Ambari 2.4.1 according:
https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.4.1
step 1:
wget
http://www.apache.org/dist/ambari/ambari-2.4.1/apache-ambari-2.4.1-src.tar.gz
(use the suggested mirror from above)
tar xfvz apache-ambari-2.4.1-src.tar.gz
cd apache-ambari-2.4.1-src
mvn versions:set -DneVersion=2.4.1.0.0
pushd ambari-metrics
mvn versions:set -DnewVersion=2.4.1.0.0
popd
when running:
mvn -B clean install package rpm:rpm -DnewVersion=2.4.1.0.0 -DskipTests
-Dpython.ver="python >= 2.6"
console throws follow:
.....
psutils-compile:
[exec] running build
[exec] running build_py
[exec] creating
/root/apache-ambari-2.4.1-src/ambari-metrics/ambari-metrics-host-monitoring/target/psutipsutil/_psutil_linux.c:12:20:
error: Python.h: No such file or directory
[exec] l_build
....
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run (psutils-compile) on
project ambari-metrics-host-monitoring: An Ant BuildException has occured: exec
returned: 1
[ERROR] around Ant part ...<exec
dir="/root/apache-ambari-2.4.1-src/ambari-metrics/ambari-metrics-host-monitoring/src/main/python/psutil"
executable="/root/apache-ambari-2.4.1-src/ambari-metrics/ambari-metrics-host-monitoring/../../ambari-common/src/main/unix/ambari-python-wrap"
failonerror="true">... @ 4:275 in
/root/apache-ambari-2.4.1-src/ambari-metrics/ambari-metrics-host-monitoring/target/antrun/build-psutils-compile.xml
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
> 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)
