You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Naveen Somasundaram (JIRA)" <ji...@apache.org> on 2015/05/15 00:25:59 UTC
[jira] [Assigned] (SAMZA-664) Support shutting down Samza job
through coordinator stream
[ https://issues.apache.org/jira/browse/SAMZA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Naveen Somasundaram reassigned SAMZA-664:
-----------------------------------------
Assignee: Naveen Somasundaram
> Support shutting down Samza job through coordinator stream
> ----------------------------------------------------------
>
> Key: SAMZA-664
> URL: https://issues.apache.org/jira/browse/SAMZA-664
> Project: Samza
> Issue Type: Improvement
> Components: container, yarn
> Reporter: Yan Fang
> Assignee: Naveen Somasundaram
>
> We have seen some use cases where people want to shutdown the Samza Job through another Samza Job. For example, after Samza job2 catches up Samza job1, job2 wants to shutdown job1. One of those cases was discussed [here|http://mail-archives.us.apache.org/mod_mbox/incubator-samza-dev/201504.mbox/%3CCAKjW-3+DLc9kx+zVY0dapOAyiW1f5KEhu=KCtrbovGkNJznCYA@mail.gmail.com%3E].
> After SAMZA-448, we can easily meet this requirement -- have the coordinator stream to accept a shutdown config/signal, and AM decides to shutdown all containers gracefully.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)