[
https://issues.apache.org/jira/browse/MAPREDUCE-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026212#comment-13026212
]
Amar Kamat commented on MAPREDUCE-2421:
---------------------------------------
Tom,
The crux of the problem is in passing JobTracker object around. Why cant we
define a new class that will take care of maintaing the jobs and their states.
The data-structure under contention is jobs (a map) and the only
wrapper/handler to it is JobTracker. Does it makes sense to break this direct
connection by introducing something like a JobsManager which only deals with
job-in-progress object management and pass this manager handle around?
Not sure if defining an interface just for the callback and making JobTracker
implement it is the right thing to do.
> Remove JobHistory's dependency on JobTracker
> --------------------------------------------
>
> Key: MAPREDUCE-2421
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2421
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: client
> Reporter: Tom White
> Assignee: Tom White
> Attachments: MAPREDUCE-2421.patch
>
>
> The direct dependency can be removed by introducing a callback inteface. This
> is for MAPREDUCE-1638.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
