[
https://issues.apache.org/jira/browse/SAMZA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098746#comment-14098746
]
Jon Bringhurst commented on SAMZA-375:
--------------------------------------
The basic design for this is in place.
The current state (how many tasks are running/allocated/etc) will be stored in
zookeeper (not implemented yet) from:
https://github.com/fintler/samza/blob/SAMZA-375/samza-mesos/src/main/scala/org/apache/samza/job/mesos/SamzaSchedulerState.scala
As mesos offers resources (resourceOffers cb), the SamzaSchedulerState is
modified by:
https://github.com/fintler/samza/blob/SAMZA-375/samza-mesos/src/main/scala/org/apache/samza/job/mesos/SamzaScheduler.scala
By keeping the state in zookeeper, the scheduler should be able to fail and
reregister() without requiring the samza tasks to restart.
Any thoughts on the overall design?
> Investigate Mesos Job Support
> -----------------------------
>
> Key: SAMZA-375
> URL: https://issues.apache.org/jira/browse/SAMZA-375
> Project: Samza
> Issue Type: Bug
> Reporter: Jon Bringhurst
> Assignee: Jon Bringhurst
>
> It would be nice if Samza had support for Mesos (https://mesos.apache.org/).
> The current plan is to create a MesosJob and MesosJobFactory, then look into
> what it would take to allow the AM code to act as a Mesos scheduler.
> The feasibility of this landing in trunk will be better understood after a
> rough prototype has been created.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
