[
https://issues.apache.org/jira/browse/GIRAPH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580257#comment-13580257
]
Hyunsik Choi commented on GIRAPH-13:
------------------------------------
The patch is looking great. In particular, GiraphYarnClient is quite neat. I
like it.
In addition to a few issues that you mentioned, the followings should be
handled (may be you already planed):
1. Are you planning to implement a history system? When a Giraph job runs on
Yarn, Giraph needs its own history system. Probably, Giraph needs a specialized
history system with a veriety of counters/metrics.
2. Should provide a way to enable users to specify a memory size of
ApplicationMaster or task containers. It would be good if both API and CLI
provide it.
Because existing I/O code is dependent on MR1, it looks hard to handle I/O code
for Yarn port. If you plan to make Giraph more platform-independent, how about
this? First, we refactor existing I/O code to be generic and
platform-independent. Then, we implement some wrapper classes for MR1. If we
did, it is easier to port Giraph to another platform.
> 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
>
>
> 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: http://www.atlassian.com/software/jira
