giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-13) Port Giraph to YARN
Date Wed, 20 Feb 2013 17:37:15 GMT


Hyunsik Choi commented on GIRAPH-13:

That's nice progress. But, is just an interface? I cannot find
from the patch.

Anyway, I vote +1 for the approach using GiraphYarnTask. I think this is reasonable and the
most simple way in the current stage. It makes the porting works easier, while we can minimize
the change of existing codes.

In addition, I agree that Yarn allows a much finer grained control throughout the whole processing.
Many interesting issues that we have not needed to consider occur if we completely port Giraph
to Yarn.
> Port Giraph to YARN
> -------------------
>                 Key: GIRAPH-13
>                 URL:
>             Project: Giraph
>          Issue Type: New Feature
>            Reporter: Jakob Homan
>            Assignee: Eli Reisman
>         Attachments: GIRAPH-13-1.patch, GIRAPH-13-2.patch, GIRAPH-13-3.patch, GIRAPH-13-4.patch
> Now that YARN (aka MR2 aka MAPREDUCE-279) has been merged into the Hadoop trunk, we should
think about what it would take to separate out the graph processing bits of Giraph from the
MR1-specific code so as to take advantage of the less-MR centric aspects of YARN, while still
supporting both over the medium term.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message