You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Charles Allen (JIRA)" <ji...@apache.org> on 2015/05/15 00:19:04 UTC

[jira] [Commented] (SAMZA-375) Investigate Mesos Job Support

    [ https://issues.apache.org/jira/browse/SAMZA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544408#comment-14544408 ] 

Charles Allen commented on SAMZA-375:
-------------------------------------

[~zcox]: Awesome.

I looked over your branch a while ago and took another very brief peek at it. One key concern I have is with framework failover, or even rolling upgrades. Do you have any particular means of reconciliation or failover for the running samza tasks?

> 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: Banno-samza-mesos-1.3.0-1-g62c624d.tar.gz, SAMZA-375.patch, Screen Shot 2014-08-23 at 5.51.39 PM.png, Screen Shot 2014-09-22 at 8.59.12 AM.png, samza-mesos-multiple-jobs.jpg
>
>
> 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)