[
https://issues.apache.org/jira/browse/HADOOP-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-3729:
-----------------------------------
Attachment: hadoop-3729.patch
tasktracker changes. I'm not convinced this is stable, but I'm going offline
for two weeks, and wanted to leave this to say "here is what to work with"
* The constructor is a bit convoluted, as unlike the other Services, a static
factory method is not used to create the class. The existing
TaskTracker(JobConf) initialises and starts the component by default, but
subclasses have the option of disabling this, which they should do.
* Cleanup threads get shut down too (HADOOP-3727) . Termination is seemingly
stable when the service is not fully started, though tests are needed for that.
* the tracker can be closed/initialized repeatedly
> Integrate TaskTracker with the Service base class
> -------------------------------------------------
>
> Key: HADOOP-3729
> URL: https://issues.apache.org/jira/browse/HADOOP-3729
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.19.0
> Reporter: Steve Loughran
> Attachments: hadoop-3729.patch
>
>
> Following on from the initial service patch, we need to bring TaskTracker
> into the fold. This separate issue does this activity
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
