[
https://issues.apache.org/jira/browse/AMBARI-15606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216112#comment-15216112
]
Hudson commented on AMBARI-15606:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.2 #565 (See
[https://builds.apache.org/job/Ambari-branch-2.2/565/])
AMBARI-15606 Ambari API does not return HDFS RPC metrics based on ports (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1936d09419d56f7dcaf5984ffffbc304894d7c53])
*
ambari-server/src/test/java/org/apache/ambari/server/controller/utilities/PropertyHelperTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/JMXPropertyProviderTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackDefinedPropertyProviderTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXHostProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/PropertyHelper.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractProviderModule.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXPropertyProvider.java
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py
> Ambari API does not return HDFS RPC metrics based on ports
> ----------------------------------------------------------
>
> Key: AMBARI-15606
> URL: https://issues.apache.org/jira/browse/AMBARI-15606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15606-trunk_2.patch
>
>
> ISSUE: Ambari API does not return HDFS RPC metrics based on ports (Example
> 8020 and 8040)
> When creating Ambari Widget we don't see an option to monitor by port. Hence
> the monitoring of Random port or aggregate doesn't give correct information
> After the patch, ambari automatically replaces port number with the
> corresponding suffix
> client for the port specified in hdfs-site/dfs.namenode.rpc-address
> datanode for the port specified in hdfs-site/dfs.namenode.servicerpc-address
> healthcheck for the port specified in
> hdfs-site/dfs.namenode.lifeline.rpc-address
> Request/response example
> {code}
> {
> "href" :
> "http://10.2.2.22:1081/api/v1/clusters/c1/services/HDFS/components/NAMENODE?fields=host_components/metrics/rpc/*,host_components/metrics/runtime/*";,
> "ServiceComponentInfo" : {
> "cluster_name" : "c1",
> "component_name" : "NAMENODE",
> "service_name" : "HDFS"
> },
> "host_components" : [
> {
> "href" :
> "http://10.2.2.22:1081/api/v1/clusters/c1/hosts/c6401.ambari.apache.org/host_components/NAMENODE";,
> "HostRoles" : {
> "cluster_name" : "c1",
> "component_name" : "NAMENODE",
> "host_name" : "c6401.ambari.apache.org"
> },
> "metrics" : {
> "rpc" : {
> "client" : {
> "NumOpenConnections" : 0,
> "ReceivedBytes" : 2508,
> "RpcProcessingTime_avg_time" : 0.0,
> "RpcProcessingTime_num_ops" : 12,
> "RpcQueueTime_avg_time" : 0.0,
> "RpcQueueTime_num_ops" : 12,
> "SentBytes" : 408,
> "callQueueLen" : 0,
> "rpcAuthenticationFailures" : 0,
> "rpcAuthenticationSuccesses" : 0,
> "rpcAuthorizationFailures" : 0,
> "rpcAuthorizationSuccesses" : 12
> },
> "datanode" : {
> "NumOpenConnections" : 2,
> "ReceivedBytes" : 3269926,
> "RpcProcessingTime_avg_time" : 0.0,
> "RpcProcessingTime_num_ops" : 6029,
> "RpcQueueTime_avg_time" : 0.0,
> "RpcQueueTime_num_ops" : 6029,
> "SentBytes" : 248169,
> "callQueueLen" : 0,
> "rpcAuthenticationFailures" : 0,
> "rpcAuthenticationSuccesses" : 0,
> "rpcAuthorizationFailures" : 0,
> "rpcAuthorizationSuccesses" : 288
> }
> },
> "runtime" : {
> "StartTime" : 1459170322047
> }
> }
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
