You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jon Bringhurst (JIRA)" <ji...@apache.org> on 2015/01/18 00:16:36 UTC

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

     [ https://issues.apache.org/jira/browse/SAMZA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon Bringhurst updated SAMZA-375:
---------------------------------
    Attachment: SAMZA-375.patch

Just so it's officially owned by Apache, I've attached a patch to this issue with the code I originally wrote. The contents are the same as:

https://github.com/fintler/samza/compare/SAMZA-375.patch

This patch isn't something we should commit to trunk without significant polish (such as the work done by [~kostassoid] and [~zcox]). It's just here to make things official.

> 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: 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)