hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-297) generalize the TT / JT servers to handle more generic tasks
Date Sun, 17 Jun 2012 10:56:44 GMT

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

Harsh J resolved MAPREDUCE-297.
-------------------------------

    Resolution: Duplicate

Resolving as dupe of MAPREDUCE-279, that has provided a way for this.

But, do reopen if I am found wrong in my interpretation of the description.
                
> generalize the TT / JT servers to handle more generic tasks
> -----------------------------------------------------------
>
>                 Key: MAPREDUCE-297
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-297
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: eric baldeschwieler
>
> We've been discussing a proposal to generalize the TT / JT servers to handle more generic
tasks and move job specific work out of the job tracker and into client code so the whole
system is both much more general and has more coherent layering.  The result would look more
like condor/pbs like systems (or presumably borg) with map-reduce as a user job.
> Such a system would allow the current map-reduce code to coexist with other work-queuing
libraries or maybe even persistent services on the same Hadoop cluster, although that would
be a stretch goal.  We'll kick off a thread with some documents soon.
> Our primary goal in going this way would be to get better utilization out of map-reduce
clusters and support a richer scheduling model.  The ability to support alternative job frameworks
would just be gravy!
> ----
> Putting this in as a place holder.  Hope to get folks talking about this to post some
more detail.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message