[
https://issues.apache.org/jira/browse/HAMA-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894242#comment-13894242
]
Jeff Fenchel commented on HAMA-726:
-----------------------------------
Has there been any progress on this feature? If not, I believe I have the time
to implement it.
I would really like it if this could be done completely in the configuration
settings so we could avoid having something like MesosJob as is currently
implemented for yarn. Along those lines, I was thinking I could implement a
mesos TaskWorker to hopefully make it compatible with future schedulers. This
will likely require that the taskWorker be given knowledge of the
groomServerManager instead of just being passed a set of statuses.
I believe the above would allow for the typical mesos framework model to be
followed by a mesos scheduler/executor where the scheduler would start and stop
groom servers wrapped in mesos executors for each job. Also, I imagine all of
this should probably be put inside a new maven module, similar to what was done
for yarn.
Is this feature still something that is wanted/being accepted by Hama? If so,
does the above plan seem reasonable?
> Hama on Mesos
> -------------
>
> Key: HAMA-726
> URL: https://issues.apache.org/jira/browse/HAMA-726
> Project: Hama
> Issue Type: New Feature
> Components: bsp core
> Reporter: Suraj Menon
>
> Since we are going to refactor our code to work on YARN, it would be nice to
> keep our abstraction levels to make it feasible to work on Mesos.
> Documentation: http://incubator.apache.org/mesos/documentation.html
> Framework development guide:
> https://github.com/mesos/mesos/wiki/App-Framework-development-guide
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
