incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-1978) Deploying HDP-1.3.0 results in several alerts - is it related to hard-coded port
Date Fri, 19 Apr 2013 22:09:16 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636929#comment-13636929
] 

Yusaku Sako commented on AMBARI-1978:
-------------------------------------

Tried the patch out on a live cluster.  The patches resolved the said issues. +1.
                
> Deploying HDP-1.3.0 results in several alerts - is it related to hard-coded port
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-1978
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1978
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent
>    Affects Versions: 1.3.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-1978.patch, AMBARI-1978.patch
>
>
> TaskTracker, RegionServer, HBase master process down because check_tcp failure.
> Looks like the hadoop-services.cfg.erb has:
> check_command           check_tcp!<%=scope.function_hdp_template_var("jtnode_port")%>!-w
1 -c 1
> and looks like the ports are not getting replaced and end up being empty.

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

Mime
View raw message