You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yan Fang (JIRA)" <ji...@apache.org> on 2015/03/06 19:56:38 UTC

[jira] [Assigned] (SAMZA-506) Shutdown container on SIGTERM

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

Yan Fang reassigned SAMZA-506:
------------------------------

    Assignee: Yan Fang

> Shutdown container on SIGTERM
> -----------------------------
>
>                 Key: SAMZA-506
>                 URL: https://issues.apache.org/jira/browse/SAMZA-506
>             Project: Samza
>          Issue Type: New Feature
>          Components: container
>    Affects Versions: 0.8.0
>            Reporter: Zach Cox
>            Assignee: Yan Fang
>             Fix For: 0.9.0
>
>
> Many runtime platforms (e.g. Mesos) will issue a SIGTERM to stop the Samza container process. In this case it would be good to try to cleanly shutdown the container, so that messages stop being processed, offsets and changelogs are committed, etc. This can be accomplished using TaskCoordinator.shutdown, but there currently is no glue between that and a SIGTERM or jvm shutdown hook.
> Here is the relevant mailing list thread: http://www.mail-archive.com/dev%40samza.incubator.apache.org/msg02246.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)