[ http://issues.apache.org/jira/browse/HADOOP-239?page=comments#action_12438487 ] Sanjay Dahiya commented on HADOOP-239: --------------------------------------
Here are some new changes ( will submit patch in a while ) Moved code to Java 5 Replaced all data attributes in JobInfo and other objects with HashMap. All key-value pairs are accessed through get(KEY), set(Key, Value) methods. All keys are defined in a single Enum, which acts like a global namespace for all keys used in job history. Adding new keys/values is now fairly simple, they need to be added to the Enum. after that these can be read/written without making any change in JobHistory implementation. does this sound reasonable? > job tracker WI drops jobs after 24 hours > ---------------------------------------- > > Key: HADOOP-239 > URL: http://issues.apache.org/jira/browse/HADOOP-239 > Project: Hadoop > Issue Type: Bug > Components: mapred > Reporter: Yoram Arnon > Assigned To: Sanjay Dahiya > Priority: Minor > Attachments: Hadoop-239.patch, Hadoop-239_1.patch > > > The jobtracker's WI, keeps track of jobs executed in the past 24 hours. > if the cluster was idle for a day (say Sunday) it drops all its history. > Monday morning, the page is empty. > Better would be to store a fixed number of jobs (say 10 each of succeeded and > failed jobs). > Also, if the job tracker is restarted, it loses all its history. > The history should be persistent, withstanding restarts and upgrades. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
