[
https://issues.apache.org/jira/browse/GIRAPH-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172813#comment-13172813
]
Ed Kohlwey commented on GIRAPH-108:
-----------------------------------
Hi Claudio,
Thanks for pointing me that way. It seems like this might be appropriate to
call a sub-task for GIRAPH-13? My eventual goal with this patch is actually to
target Mesos, and 13 seems to be targeting YARN.
It seems like it shouldn't be too hard to maintain a few drivers, one for M/R,
one for YARN, and one for Mesos - most of the daemon code is pretty well
abstracted and shouldn't take a lot of work to port to the other frameworks.
> Refactor code to run independently of Map/Reduce
> ------------------------------------------------
>
> Key: GIRAPH-108
> URL: https://issues.apache.org/jira/browse/GIRAPH-108
> Project: Giraph
> Issue Type: Improvement
> Components: graph
> Reporter: Ed Kohlwey
> Attachments: GIRAPH-108
>
>
> It would be nice for Giraph to be refactored such that the code could
> eventually be run outside of map/reduce. This will allow people to write
> drivers that can run in the cool new resource manager frameworks like Mesos
> and YARN, and eventually let the application's code base evolve to be
> independent of map/reduce.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
