giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Reisman (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-737) Giraph Application Master: move to new and stable YARN API
Date Sun, 01 Sep 2013 06:15:52 GMT


Eli Reisman commented on GIRAPH-737:

Originally, the concept was to be compatible with as much of the 2.0.x-alpha Hadoop line as
possible. To this end, I attempted to use as much of the "old" YARN API as I could get away
with, figuring we could update later and end back compatibility if we ever wanted to.

Now that the 2.1-beta line is out, I think it makes a lot of sense to reevaluate this and
move forward, refactoring to the newer YARN API and perhaps even abandon 2.0.x Hadoop in favor
of the 2.1 beta line.

Need to see some code (of course) but I'm fully +1 on the idea. Anyone else want to chime
in here?

> Giraph Application Master: move to new and stable YARN API
> ----------------------------------------------------------
>                 Key: GIRAPH-737
>                 URL:
>             Project: Giraph
>          Issue Type: New Feature
>          Components: mapreduce
>            Reporter: Mohammad Kamrul Islam
>            Assignee: Mohammad Kamrul Islam
> Giraph was the early adopter of Hadoop YARN AM! Eli successfully wrote a Giraph AM based
on Hadoop 2.0.x_alpha. However, in last few months, Yarn significantly *overhauled* its APIs
and associated coding patterns. The new beta version is 2.1.x and I was told by Yarn-dev that
current APIs will not change much.
> In the above circumstances, we need to substantially overhaul Giraph AM as well to accommodate
with the new Yarn API. Moreover, in newer YARN API, supporting kerberos security in AM becomes
easier and more transparent.
> Potential impact:
> The upcoming Girpah AM will not work with earlier alpha Hadoop versions such as 2.0.3.
I'm not sure if anyone is using Giraph AM in production. However, the more prevalent way of
Giraph processing (MR-based) should continue to work.

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