You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Anthony MOI (JIRA)" <ji...@apache.org> on 2013/10/17 15:18:43 UTC
[jira] [Created] (MAPREDUCE-5588) TaskTrackers get killed by
JettyBugMonitor because of incredibly high cpu usage
Anthony MOI created MAPREDUCE-5588:
--------------------------------------
Summary: TaskTrackers get killed by JettyBugMonitor because of incredibly high cpu usage
Key: MAPREDUCE-5588
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5588
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: tasktracker
Affects Versions: 1.1.2
Reporter: Anthony MOI
We are running a little cluster with 10 servers running task trackers. All of them are getting killed randomly with the following message
{quote}
2013-10-17 11:32:31,037 FATAL org.apache.hadoop.mapred.JettyBugMonitor: ************************************************************
Jetty CPU usage: 120093277.1%. This is greater than the fatal threshold mapred.tasktracker.jetty.cpu.threshold.fatal. Aborting JVM.
************************************************************
2013-10-17 11:32:31,039 INFO org.apache.hadoop.mapred.TaskTracker: SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down TaskTracker
************************************************************/
{quote}
Everytime, the message notices a cpu usage above 120M%. Everything has been running for a while now (since 1.1.2 release) without any problems, and it started just like that.
Any idea of what could cause this ?
--
This message was sent by Atlassian JIRA
(v6.1#6144)