You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Michael Bieniosek (JIRA)" <ji...@apache.org> on 2007/10/06 01:44:50 UTC
[jira] Commented: (HADOOP-2001) Deadlock in jobtracker
[ https://issues.apache.org/jira/browse/HADOOP-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532798 ]
Michael Bieniosek commented on HADOOP-2001:
-------------------------------------------
I could submit a quick fix patch that unmarks JobTracker.finalizeJob synchronized, but I don't really know if that would break other things, or if it could miss other deadlock paths.
Anybody else know more about this code?
> Deadlock in jobtracker
> ----------------------
>
> Key: HADOOP-2001
> URL: https://issues.apache.org/jira/browse/HADOOP-2001
> Project: Hadoop
> Issue Type: Bug
> Affects Versions: 0.14.0
> Reporter: Michael Bieniosek
> Priority: Critical
>
> My jobtracker deadlocked; the output from kill -QUIT is:
> Found one Java-level deadlock:
> =============================
> "IPC Server handler 2 on 10001":
> waiting to lock monitor 0x0813724c (object 0xd5175488, a org.apache.hadoop.mapred.JobInProgress),
> which is held by "SocketListener0-1"
> "SocketListener0-1":
> waiting to lock monitor 0x081146d4 (object 0xd24d9c50, a org.apache.hadoop.mapred.JobTracker),
> which is held by "IPC Server handler 2 on 10001"
> Java stack information for the threads listed above:
> ===================================================
> "IPC Server handler 2 on 10001":
> at org.apache.hadoop.mapred.JobInProgress.updateTaskStatus(JobInProgress.java:367)
> - waiting to lock <0xd5175488> (a org.apache.hadoop.mapred.JobInProgress)
> at org.apache.hadoop.mapred.JobTracker.updateTaskStatuses(JobTracker.java:1719)
> at org.apache.hadoop.mapred.JobTracker.processHeartbeat(JobTracker.java:1240)
> - locked <0xd24d9c50> (a org.apache.hadoop.mapred.JobTracker)
> at org.apache.hadoop.mapred.JobTracker.heartbeat(JobTracker.java:1116)
> - locked <0xd24d9c50> (a org.apache.hadoop.mapred.JobTracker)
> at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:340)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:566)
> "SocketListener0-1":
> at org.apache.hadoop.mapred.JobTracker.finalizeJob(JobTracker.java:907)
> - waiting to lock <0xd24d9c50> (a org.apache.hadoop.mapred.JobTracker)
> at org.apache.hadoop.mapred.JobInProgress.garbageCollect(JobInProgress.java:1059)
> - locked <0xd5175488> (a org.apache.hadoop.mapred.JobInProgress)
> at org.apache.hadoop.mapred.JobInProgress.kill(JobInProgress.java:891)
> - locked <0xd5175488> (a org.apache.hadoop.mapred.JobInProgress)
> at org.apache.hadoop.mapred.jobdetails_jsp._jspService(jobdetails_jsp.java:158)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:427)
> at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:475)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1565)
> at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:635)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1517)
> at org.mortbay.http.HttpServer.service(HttpServer.java:954)
> at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
> at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981)
> at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
> at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
> at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
> at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
> Found 1 deadlock.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.