ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-4313) HistoryServer alerts on 1.3.4 stack
Date Thu, 16 Jan 2014 14:01:22 GMT

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

Andrew Onischuk updated AMBARI-4313:
------------------------------------

    Attachment: AMBARI-4313.patch

> HistoryServer alerts on 1.3.4 stack
> -----------------------------------
>
>                 Key: AMBARI-4313
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4313
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-4313.patch
>
>
> After deploying 1.3.4 stack following alerts appears:
> {code}
> HistoryServer RPC latency
> CRIT for 25 minutes
> CRITICAL: Data inaccessible, Status code = 0
> HistoryServer process
> CRIT for 28 minutes
> Connection refused
> HistoryServer Web UI
> WARN for 27 minutes
> WARNING: HistoryServer Web UI not accessible : http://c6402.ambari.apache.org:19888/jobhistory
> {code}
> Restarting HistoryServer and MapReduce didn't solve the problem. This problem is not
reproducible every time, but for me it reproduces constantly.
> Please see screenshot and logs attached. BTW, all quick links on MapReduce page seems
live. 
> And there is a quicklink "JobHistory Server" that points to: http://c6402.ambari.apache.org:51111/jobhistoryhome.jsp
and its working.
> It's not very clear, is JobHistory Server and History Server the same thing, and why
Nagios checks http://c6402.ambari.apache.org:19888/jobhistory.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message