[
https://issues.apache.org/jira/browse/SAMZA-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826853#comment-15826853
]
Yi Pan (Data Infrastructure) commented on SAMZA-516:
----------------------------------------------------
[~amalhotra], yes, we recognize the need from the community. The current effort
was shifted to SAMZA-1063. Please take a look at the refreshed design and
comment.
P.S. some of the sub-tasks here may also be superseded by newer tasks under
SAMZA-1063. We will update here. Thanks!
> Support standalone Samza jobs
> -----------------------------
>
> Key: SAMZA-516
> URL: https://issues.apache.org/jira/browse/SAMZA-516
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.9.0
> Reporter: Chris Riccomini
> Assignee: Chris Riccomini
> Labels: design, project
> Attachments: DESIGN-SAMZA-516-0.md, DESIGN-SAMZA-516-0.pdf,
> DESIGN-SAMZA-516-1.md, DESIGN-SAMZA-516-1.pdf, DESIGN-SAMZA-516-2.md,
> DESIGN-SAMZA-516-2.pdf
>
>
> Samza currently supports two modes of operation out of the box: local and
> YARN. With local mode, a single Java process starts the JobCoordinator,
> creates a single container, and executes it locally. All partitions are
> procesed within this container. With YARN, a YARN grid is required to
> execute the Samza job. In addition, SAMZA-375 introduces a patch to run Samza
> in Mesos.
> There have been several requests lately to be able to run Samza jobs without
> any resource manager (YARN, Mesos, etc), but still run it in a distributed
> fashion.
> The goal of this ticket is to design and implement a samza-standalone module,
> which will:
> # Support executing a single Samza job in one or more containers.
> # Support failover, in cases where a machine is lost.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
