[
https://issues.apache.org/jira/browse/SAMZA-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Kleppmann resolved SAMZA-253.
------------------------------------
Resolution: Fixed
Committed to both the master and the 0.7.0 branches. Resolving.
> Consensus shutdown API
> ----------------------
>
> Key: SAMZA-253
> URL: https://issues.apache.org/jira/browse/SAMZA-253
> Project: Samza
> Issue Type: New Feature
> Reporter: Martin Kleppmann
> Assignee: Martin Kleppmann
> Fix For: 0.7.0
>
> Attachments: SAMZA-253.1.patch, SAMZA-253.3.patch,
> SAMZA-253.final.patch
>
>
> Extracted from SAMZA-179.
> At the moment, TaskCoordinator.shutdown() can be called by any task, and
> immediately shuts down the container as soon as the current message has
> finished processing. That is appropriate in some cases, but not always.
> Sometimes, what we actually want is for each task to vote that it's ready to
> shut down, and for the container to be shut down when all tasks within that
> container have voted.
> A first implementation of this is on https://reviews.apache.org/r/19384/ but
> it's mixed up with several other concerns. This ticket is to extract only the
> shutdown API changes (TaskCoordinator.ShutdownMethod) from that patch, and to
> address the relevant comments made on that RB.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
