[ https://issues.apache.org/jira/browse/MAPREDUCE-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated MAPREDUCE-1436: ----------------------------------- Attachment: deadlock.png Hey Matei. Here's another potential deadlock. Now that I see this one, I realize I actually ran into the one you're fixing here before - I had thought it was unique to the unit tests, but I think it really is a problem. Can you take a look at this cycle and see what you think? If it's a separate issue, maybe we can do it in a new jira. Thanks. > Deadlock in preemption code in fair scheduler > --------------------------------------------- > > Key: MAPREDUCE-1436 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1436 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: contrib/fair-share > Affects Versions: 0.21.0, 0.22.0 > Reporter: Matei Zaharia > Assignee: Matei Zaharia > Priority: Blocker > Attachments: deadlock.png, mapreduce-1436.patch > > > In testing the fair scheduler with preemption, I found a deadlock between > updatePreemptionVariables and some code in the JobTracker. This was found > while testing a backport of the fair scheduler to Hadoop 0.20, but it looks > like it could also happen in trunk and 0.21. Details are in a comment below. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.