[
https://issues.apache.org/jira/browse/MAPREDUCE-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446029#comment-13446029
]
Tom White commented on MAPREDUCE-4488:
--------------------------------------
Karthik - thanks for investigating. Regarding your fix, it would be better to
reduce the scope of the lock on JT to the {{job.initTasks()}} statement.
However even this might be excessively wide since initTasks() reads input split
files, etc.
There might be a way of reducing the scope of the synchronization on
JobInProgress in initTasks() so that it can take a lock on the JT first before
making the setupComplete() call. But as Arun rightly points out the locking in
JT is very delicate so we have to be conservative here, so at least having a
clean jcarder run would be prudent.
> Port MAPREDUCE-463 (The job setup and cleanup tasks should be optional) to
> branch-1
> -----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4488
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4488
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv1, performance
> Affects Versions: 1.0.3
> Reporter: Tom White
> Assignee: Tom White
> Attachments: fix-mr-4488.patch, MAPREDUCE-4488.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
