[
https://issues.apache.org/jira/browse/SAMZA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149315#comment-14149315
]
Chris Riccomini commented on SAMZA-375:
---------------------------------------
[~joestein], [~tnachen], one thing that you guys might be able to clear up for
us is how we're supposed to build the equivalent of YARN's AM. Jon and I are
both pretty new to Mesos, and it's unclear what the right architecture is.
In the YARN world, we have one ApplicationMaster (AM) per-Samza job. Each of
these ApplicationMasters is responsible for coordinating amongst its containers
(executors in Mesos, I believe). The AM is responsible for requesting
resources, and defining what runs on each executor, and what to do when one of
the executors fails.
In Jon's current patch, we have basically converted the YARN AM to a framework.
Thus, each Samza job appears as its own "framework" in the Mesos UI. This seems
kind of odd. I'm wondering if we have the wrong abstraction, and we should
instead of one Samza framework which coordinates amongst *all* Samza jobs on a
single Mesos cluster.
Can you guys provide some guidance 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, project
> Attachments: Screen Shot 2014-08-23 at 5.51.39 PM.png, Screen Shot
> 2014-09-22 at 8.59.12 AM.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.3.4#6332)
