hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Jungblut (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-431) MapReduce NG integration
Date Wed, 14 Sep 2011 06:28:17 GMT

    [ https://issues.apache.org/jira/browse/HAMA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104292#comment-13104292

Thomas Jungblut commented on HAMA-431:

Thanks Vinod,

We can work with patches, but that won't scale. I think we need to get commit privileges with
a promise to restrict ourselves to a branch. I noticed Edward is off for a week, may be he
can pull some strings when he's back?

He pulled some strings yesterday. My account is on its way. I guess we can start in 1-2 days.

If this isn't already there in V1, it makes sense to take this up as a follow up to the first
cut of V2.

Yes, but I think we should take things like TaskAttempts into account.
The roll-back of an attempt will be another task and should be scheduled for V2. The extending
of the state machine for handling these events will be another task, too.

So our first version will solely be:

* Message passing between peers
* Barrier Sync with control of the ApplicationMaster
* Job submission via the current BSPJob Class.

And the statemachine will just be: 

Anything else we should take into account?
@ChiaHung do you want to help us?

> MapReduce NG integration
> ------------------------
>                 Key: HAMA-431
>                 URL: https://issues.apache.org/jira/browse/HAMA-431
>             Project: Hama
>          Issue Type: New Feature
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
> We should take a look at how to integrate Hama's BSP Engine to Hadoop's nextGen application
> Can be currently found in the 0.23 branch.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message