[
https://issues.apache.org/jira/browse/GIRAPH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602552#comment-13602552
]
Eli Reisman commented on GIRAPH-13:
-----------------------------------
I found one small problem that crops up sometimes when running mvn verify
involving test directory name collisions with InternalVertexRunner when using
MiniYARNCLuster. MiniYARNCluster can easily end up using the same dirs or ZK
ports (or wrong ZK instance) during Maven testing. I have fixed it but will
temporarily withhold the patch spam for now in case I:
1. find more little things to fix
2. or folks put up some review issues
Anyway, if you're feeling brave enough to install 2.0.3-alpha and test this,
let me know and I'll update the patch sooner. Also ping me about YARN install
issues, there are a couple little things that need to happen that are not
entirely well documented and big for us.
> 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
>
>
> 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
