ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (AMBARI-12563) Ambari return fail upon service check
Date Thu, 30 Jul 2015 22:25:04 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-12563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Siddharth Wagle reopened AMBARI-12563:
--------------------------------------

HDFS alerts going to the Namenode and Secondary Namenode JMX still show up as Connection refused
followed by the motd message above.

Need a fix on the alert code path as well.


> Ambari return fail upon service check 
> --------------------------------------
>
>                 Key: AMBARI-12563
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12563
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.1.1
>
>
> User has a third party monitoring tool that, whenever user do a
> 'su' it prints out the following message
> Hello user, have fun!
> Therefore, for example when user starts up namenode, Ambari is not able to
> phrase the status codes after executing the curl call for webHDFS, and throw
> error message and indicates the operation as fail. Meanwhile, the namenode is
> actually up and running.  
> This behavior also happens across other services, such as HBase.
> This issue is causing confusion upon starting of
> services/components.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message