[ 
https://issues.apache.org/jira/browse/MAPREDUCE-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988338#action_12988338
 ] 

Scott Chen commented on MAPREDUCE-1825:
---------------------------------------

> 2) FairSchedulerServlet is locking up in showPools method as soon as it tries 
> to synchronize on "scheduler". It continues again as soon as JIB.initTasks() 
> finish. Not sure how this is happening as initTasks() lock JIB's monitor and 
> showPools lock scheduler's monitor. Anyway, the patch doesn't seem to address 
> the FSS issue.

Thanks for the testing, Priyo.
Can you take a jstack at the moment that it waits for scheduler?
Then we can figure out the lock dependency.

> jobqueue_details.jsp and FairSchedulerServelet should not call finishedMaps 
> and finishedReduces when job is not initialized
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1825
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1825
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>    Affects Versions: 0.20.1
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Scott Chen
>             Fix For: 0.22.0
>
>         Attachments: MAPREDUCE-1825.txt, MAPREDUCE-1825_1.txt, 
> MAPREDUCE-1825_2.txt
>
>
> JobInProgress.finishedMaps() and finishedReduces() are synchronized. They are 
> called from jobqueue_details.jsp and FairSchedulerServelet which iterates 
> through all jobs. If any job is in initialization, these pages don't come up 
> until the initialization finishes.
> See 
> [comment|https://issues.apache.org/jira/browse/MAPREDUCE-1354?focusedCommentId=12834139&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12834139]
>  for more details

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to