[
https://issues.apache.org/jira/browse/SAMZA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149761#comment-14149761
]
Timothy Chen commented on SAMZA-375:
------------------------------------
Hi [~criccomini] [~jonbringhurst],
A framework in Mesos is associated to one role (for now) into Mesos master, and
Mesos schedules and distribute resources according to a role:weight mapping.
For example, if Samza and Hadoop each come up as "samza" and "hadoop" role and
their weight is 3:1, then samza will get 3/4 of the cluster resources and
hadoop 1/4, where default each has weight of one.
So if you create a framework per job then mesos will start have a unevenness of
resource managing.
So I think we should model Samza as a whole as a single framework. The good
thing about a Mesos framework is that itself can schedule how to allocate the
given resources itself to what executors, and it can be dynamic by keeping its
own mapping in the framework samza job -> list <executor>
I haven't really dived much into Samza except the high level understanding I
got during the time I was at LI.
Where can I take a look what a yarn container is currently doing?
> 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)
