[
https://issues.apache.org/jira/browse/SAMZA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149894#comment-14149894
]
Jon Bringhurst commented on SAMZA-375:
--------------------------------------
Hey [~tnachen], in terms of this image (https://i.imgur.com/PSIduMX.png), the
AM is mostly centered around onContainerAllocated in
https://github.com/apache/incubator-samza/blob/350909d6c250fa1ae4d68c0c9b144ca756f84cf1/samza-yarn/src/main/scala/org/apache/samza/job/yarn/SamzaAppMasterTaskManager.scala#L106
, the client is basically
https://github.com/apache/incubator-samza/blob/master/samza-yarn/src/main/scala/org/apache/samza/job/yarn/YarnJobFactory.scala
, and the Yarn container is wrapped with
https://github.com/apache/incubator-samza/blob/master/samza-yarn/src/main/scala/org/apache/samza/job/yarn/YarnContainer.scala
.
It might be useful to start from YarnJobFactory to see the setup, then review
the path from SamzaAppMaster to YarnAppMasterListener/SamzaAppMasterTaskManager.
> 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)
