[
https://issues.apache.org/jira/browse/GIRAPH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605408#comment-13605408
]
Eli Reisman commented on GIRAPH-13:
-----------------------------------
Hey Eugene, a better command line is on the current revision of this patch on
RB (marked r5 there, its r4 in the patch here...sorry) in the explanation.
Forgot to post it here. And yes, there are several yarn-site.xml values you
need set I can pass along that are not well doc'ed that make the cluster happy
if you run into trouble.
So far, this version works well for me.
> Port Giraph to YARN
> -------------------
>
> Key: GIRAPH-13
> URL: https://issues.apache.org/jira/browse/GIRAPH-13
> 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, GIRAPH-13-5.patch, GIRAPH-13-6.patch, GIRAPH-13-7.patch,
> GIRAPH-13-8.patch, GIRAPH-13-9.patch, GIRAPH-13-9-r1.patch,
> GIRAPH-13-9-r2.patch, GIRAPH-13-9-r3.patch, GIRAPH-13-9-r4.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.
> Review Board link (ready for review now): https://reviews.apache.org/r/9811/
--
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: http://www.atlassian.com/software/jira
