[
https://issues.apache.org/jira/browse/AMBARI-15415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195270#comment-15195270
]
Hudson commented on AMBARI-15415:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.2 #512 (See
[https://builds.apache.org/job/Ambari-branch-2.2/512/])
Revert "AMBARI-15415. Fix new HDFS AMS alerts to account for NN rpc (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d7f47f14adfa5d8d5b8b1350357a52f9a4c3a5ab])
*
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/alerts.json
> Fix new HDFS AMS alerts to account for NN rpc ports
> ---------------------------------------------------
>
> Key: AMBARI-15415
> URL: https://issues.apache.org/jira/browse/AMBARI-15415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.2
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 2.2.2
>
> Attachments: AMBARI-15415.patch
>
>
> AMBARI-15293, changed the metric names for rpc and rpcdetailed metrics for NN
> based on the port configuration for client / datanode / healthcheck rpc
> We need a fix this by cloning the alert definition that we have into 2
> different alerts for Client / DN ports.
> *Note*: By default client and DN RPC ports are the same 8020 and for this
> case DN rpc alert should be a NOOP.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
