[
https://issues.apache.org/jira/browse/SAMZA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151993#comment-14151993
]
Jon Bringhurst commented on SAMZA-375:
--------------------------------------
Here's a whiteboard sketch of what I currently have in my head for a
multiple-job architecture using the current design in my github repo.
https://i.imgur.com/rnnBXO0.jpg (sorry about the blurriness).
Some parts are interchangeable (like marathon, the org-specific front-end, and
haproxy), but this should give you an idea of what I'm thinking in general. The
main benefit that I see to running a scheduler per-job is the ability to easily
run multiple versions of Samza, which would then allow us to upgrade Samza jobs
one-by-one.
> 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)
