You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2016/03/28 20:14:25 UTC

[jira] [Created] (AMBARI-15606) Ambari API does not return HDFS RPC metrics based on ports

Dmytro Sen created AMBARI-15606:
-----------------------------------

             Summary: 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


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)