hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-291) Optionally a separate daemon should serve JobHistory
Date Mon, 21 Jul 2014 18:14:43 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Allen Wittenauer resolved MAPREDUCE-291.

    Resolution: Fixed

I'm starting to find it hilarious that we add major features to the system and never close
their jiras out.

> Optionally a separate daemon should serve JobHistory
> ----------------------------------------------------
>                 Key: MAPREDUCE-291
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-291
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker
>            Reporter: Arun C Murthy
>            Assignee: Amar Kamat
>         Attachments: HADOOP-5083-v1.11.11.patch, HADOOP-5083-v1.11.4.patch, HADOOP-5083-v1.11.5.patch,
HADOOP-5083-v1.11.9.patch, HADOOP-5083-v1.2.patch, HADOOP-5083-v1.9.4.patch, HADOOP-5083-v1.9.patch
> Currently the JobTracker serves the JobHistory to end-users off files local-disk/hdfs.
While running very large clusters with a large user-base might result in lots of traffic for
job-history which needlessly taxes the JobTracker. The proposal is to have an optional daemon
which handles serving of job-history requests.

This message was sent by Atlassian JIRA

View raw message