giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Reisman (JIRA)" <>
Subject [jira] [Updated] (GIRAPH-13) Port Giraph to YARN
Date Wed, 20 Feb 2013 10:07:20 GMT


Eli Reisman updated GIRAPH-13:

    Attachment: GIRAPH-13-4.patch

What do you think of this approach. I have added to replace GraphMapper.
I think I may have stumbled on a method to get Giraph up and running on YARN right away, and
save the IO refactor for a future JIRA. Please let me know if some form of this approach (illustrated
in GiraphYarnTask) seems reasonable. If successful, it will allow us to stitch in pure YARN
(at least at first) with one one use of the munge flag, in only one file!

If not, I'll put up a separate JIRA to refactor Mapper#Context soon and continue to hack away
on this. When I get a chance tomorrow I will run this on test cluster and see what happens
as well.

> 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