You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2014/01/16 15:01:21 UTC

[jira] [Created] (AMBARI-4313) HistoryServer alerts on 1.3.4 stack

Andrew Onischuk created AMBARI-4313:
---------------------------------------

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