[
https://issues.apache.org/jira/browse/HADOOP-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683359#action_12683359
]
Vinod K V commented on HADOOP-5534:
-----------------------------------
{code}
Found one Java-level deadlock:
=============================
"1774437...@qtp0-45":
waiting to lock monitor 0x0000000044597ee8 (object 0x00002aab6eae1c20, a
org.apache.hadoop.mapred.FairScheduler),
which is held by "758568...@qtp0-35"
"758568...@qtp0-35":
waiting to lock monitor 0x00000000448d7428 (object 0x00002aab6eac86b0, a
org.apache.hadoop.mapred.JobTracker),
which is held by "IPC Server handler 30 on 50300"
"IPC Server handler 30 on 50300":
waiting to lock monitor 0x0000000044597ee8 (object 0x00002aab6eae1c20, a
org.apache.hadoop.mapred.FairScheduler),
which is held by "758568...@qtp0-35"
Java stack information for the threads listed above:
===================================================
"1774437...@qtp0-45":
at
org.apache.hadoop.mapred.FairSchedulerServlet.showPools(FairSchedulerServlet.java:146)
- waiting to lock <0x00002aab6eae1c20> (a
org.apache.hadoop.mapred.FairScheduler)
at
org.apache.hadoop.mapred.FairSchedulerServlet.doGet(FairSchedulerServlet.java:134)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
"758568...@qtp0-35":
at
org.apache.hadoop.mapred.JobTracker.getClusterStatus(JobTracker.java:2849)
- waiting to lock <0x00002aab6eac86b0> (a
org.apache.hadoop.mapred.JobTracker)
at org.apache.hadoop.mapred.FairScheduler.update(FairScheduler.java:337)
at
org.apache.hadoop.mapred.FairSchedulerServlet.doGet(FairSchedulerServlet.java:114)
- locked <0x00002aab6eae1c20> (a org.apache.hadoop.mapred.FairScheduler)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
"IPC Server handler 30 on 50300":
at
org.apache.hadoop.mapred.FairScheduler.assignTasks(FairScheduler.java:222)
- waiting to lock <0x00002aab6eae1c20> (a
org.apache.hadoop.mapred.FairScheduler)
at org.apache.hadoop.mapred.JobTracker.heartbeat(JobTracker.java:2368)
- locked <0x00002aab6eac86b0> (a org.apache.hadoop.mapred.JobTracker)
at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:508)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:959)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:955)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:953)
Found 1 deadlock.
{code}
> Deadlock triggered by FairScheduler scheduler's servlet due to changes from
> HADOOP-5214.
> ----------------------------------------------------------------------------------------
>
> Key: HADOOP-5534
> URL: https://issues.apache.org/jira/browse/HADOOP-5534
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/fair-share
> Affects Versions: 0.20.0
> Reporter: Vinod K V
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
