You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2013/06/26 19:04:21 UTC

[jira] [Created] (AMBARI-2497) Remove dependence on dfs_datanode_http_address global for Nagios checks

Vitaly Brodetskyi created AMBARI-2497:
-----------------------------------------

             Summary: Remove dependence on dfs_datanode_http_address global for Nagios checks
                 Key: AMBARI-2497
                 URL: https://issues.apache.org/jira/browse/AMBARI-2497
             Project: Ambari
          Issue Type: Improvement
          Components: agent
    Affects Versions: 1.2.5
            Reporter: Vitaly Brodetskyi
            Priority: Critical
             Fix For: 1.2.5


ambari-agent/src/main/puppet/modules/hdp-nagios/templates/hadoop-services.cfg.erb shows the following:
{code}
# HDFS::DATANODE Checks
define service {
        hostgroup_name          slaves
        use                     hadoop-service
        service_description     DATANODE::DataNode process down
        servicegroups           HDFS
        check_command           check_tcp!<%=scope.function_hdp_template_var("dfs_datanode_http_address")%>!-w 1 -c 1
        normal_check_interval   1
        retry_check_interval    0.5
        max_check_attempts      3
}

define service {
        hostgroup_name          slaves
        use                     hadoop-service
        service_description     DATANODE::DataNode storage full
        servicegroups           HDFS
        check_command           check_datanode_storage!<%=scope.function_hdp_template_var("dfs_datanode_http_address")%>!90%!90%
        normal_check_interval   5
        retry_check_interval    1
        max_check_attempts      2
}
{code}

We need to remove dependence on dfs_datanode_http_address and use the actual config property like:
{code}
hdp_get_port_from_url($hdfs-site["dfs.datanode.http.address"])
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira