[
https://issues.apache.org/jira/browse/GIRAPH-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814711#comment-13814711
]
Hudson commented on GIRAPH-737:
-------------------------------
SUCCESS: Integrated in Giraph-trunk-Commit #1361 (See
[https://builds.apache.org/job/Giraph-trunk-Commit/1361/])
GIRAPH-737: Giraph Application Master: Move to new and stable YARN API (mislam
via ereisman) (ereisman:
http://git-wip-us.apache.org/repos/asf?p=giraph.git&a=commit&h=3a20c5597c4f7ca67421eb39fd426cc8b0cbef2d)
* README
* giraph-core/src/main/java/org/apache/giraph/yarn/GiraphApplicationMaster.java
*
giraph-core/src/main/java/org/apache/giraph/comm/netty/handler/SaslServerHandler.java
* CHANGELOG
* findbugs-exclude.xml
* giraph-core/src/main/java/org/apache/giraph/yarn/GiraphYarnClient.java
* giraph-core/src/main/java/org/apache/giraph/comm/netty/SaslNettyServer.java
* pom.xml
* giraph-core/src/main/java/org/apache/giraph/yarn/YarnUtils.java
> Giraph Application Master: move to new and stable YARN API
> ----------------------------------------------------------
>
> Key: GIRAPH-737
> URL: https://issues.apache.org/jira/browse/GIRAPH-737
> Project: Giraph
> Issue Type: New Feature
> Components: mapreduce
> Reporter: Mohammad Kamrul Islam
> Assignee: Mohammad Kamrul Islam
> Attachments: GIRAPH-737-2.patch, GIRAPH-737-3.patch,
> GIRAPH-737.WIP.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
