You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/18 22:06:10 UTC
[jira] [Resolved] (MAPREDUCE-500) Clean up the JobTracker code
[ https://issues.apache.org/jira/browse/MAPREDUCE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved MAPREDUCE-500.
----------------------------------------
Resolution: Incomplete
Closing this as stale.
> Clean up the JobTracker code
> ----------------------------
>
> Key: MAPREDUCE-500
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-500
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Steve Loughran
> Priority: Minor
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> My IDE flags a lot of trouble in the JobTracker code, but I dont want to mix those changes with any lifecycle changes. After doing that, then I'd like to clean up the code in JobTracker
> -move to generic types and foreach loops over Vector and iterators.
> -give all threads the correct type
> -stop using package scoped static variables to pass instance-data around specifically
> TASKTRACKER_EXPIRY_INTERVAL
> RETIRE_JOB_CHECK_INTERVAL
> RETIRE_JOB_INTERVAL
> -fix up all the javadoc warnings
> -remove the needless this. references on lots of local variables
> -replace the log + stringifyException with log(text,exception).
> Its only an hour or so of work, and would improve the code maintainability, but it would make merging existing code harder.
--
This message was sent by Atlassian JIRA
(v6.2#6252)