[
https://issues.apache.org/jira/browse/MAPREDUCE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728396#action_12728396
]
Matei Zaharia commented on MAPREDUCE-729:
-----------------------------------------
Yup, that would be great.
Maybe we can also add some other methods that schedulers call in the JT into
this interface. For example, in the fair scheduler code, there are three places
where I still cast the TaskTrackerManager to a JobTracker:
* When calling getJobTrackerMachine() on it to figure out how to name my log
file
* When calling getNextHeartbeatInterval() for MAPREDUCE-548
* When adding a servlet to it for the fair scheduler UI (this is kind of hacky
so I'm okay with it not being in the interface)
I'm not sure whether there are similar casts in the other schedulers.
> Create a MapReduceMaster interface for the JobTracker
> -----------------------------------------------------
>
> Key: MAPREDUCE-729
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-729
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobtracker
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Fix For: 0.21.0
>
>
> It would be useful to have a 'master' interface which specifies all the
> interfaces exposed by the JobTracker to allow for mock-objects, simulation
> (MAPREDUCE-728) etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
