[
https://issues.apache.org/jira/browse/SAMZA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110889#comment-14110889
]
Chris Riccomini commented on SAMZA-375:
---------------------------------------
bq. Each Samza job would run as a framework which manages tasks within a single
job (the scheduler). Then, another "meta-framework" (a phrase that mesosphere
seems to be using) would run to manage each of the frameworks for the Samza
jobs. Initially, the meta-framework would be something like Marathon or Aurora,
but could later evolve into a Samza-specific meta-framework
Cool, this makes sense to me.
> Investigate Mesos Job Support
> -----------------------------
>
> Key: SAMZA-375
> URL: https://issues.apache.org/jira/browse/SAMZA-375
> Project: Samza
> Issue Type: Bug
> Components: hello-samza
> Reporter: Jon Bringhurst
> Assignee: Jon Bringhurst
> Labels: mesos
> Attachments: Screen Shot 2014-08-23 at 5.51.39 PM.png
>
>
> 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)
