[ https://issues.apache.org/jira/browse/MAPREDUCE-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Chen updated MAPREDUCE-1825: ---------------------------------- Attachment: MAPREDUCE-1825.txt FairSchedulerServlet suffer from this problem seriously because it holds the JobTracker lock while looping through jobs. So fixing this is important for FairScheduler. I make both pages skip the uninitialized jobs. Do you think this is a right fix? I am still thinking how to test it. Any suggestion on the unit test? > 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 > > > 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.