[
https://issues.apache.org/jira/browse/SAMZA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109263#comment-14109263
]
Chris Riccomini commented on SAMZA-375:
---------------------------------------
This is awesome! I'm very excited to see progress here. Once you've got things
running, let us know, and we can provide suggestions on how to make it
trunk-ready.
One question regarding the screencap. I'm not terribly familiar with Mesos.
Based on the UI, it looks like it's looking at each Samza job as an independent
"framework". Is this the suggested way to integrate Samza with Mesos, or do we
need to provide some kind of scheduler, which Mesos sees just one of, and is
"the framework"? I could see us wanting to move the YARN AM logic to a single
centralized UI in Mesos, which plugs into Mesos. This UI/service could then
manage all jobs.
I'm just not too clear on what the standard pattern is here.
> 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)
