You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/07/20 20:45:01 UTC
[jira] [Commented] (SAMZA-1368) make sure that a new job model will
be generated if zk barrier times out.
[ https://issues.apache.org/jira/browse/SAMZA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095338#comment-16095338 ]
ASF GitHub Bot commented on SAMZA-1368:
---------------------------------------
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/247
SAMZA-1368: make sure new job model will be generated in case of barrier timeout.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza onBarrierTimeout1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/samza/pull/247.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #247
----
commit 8dc9e342179c788ac30eb3b3cae8fba5a6ad4184
Author: Boris Shkolnik <bo...@apache.org>
Date: 2017-07-20T20:37:02Z
make sure new job model will be generated in case of barrier timeout
----
> make sure that a new job model will be generated if zk barrier times out.
> -------------------------------------------------------------------------
>
> Key: SAMZA-1368
> URL: https://issues.apache.org/jira/browse/SAMZA-1368
> Project: Samza
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
>
> When barrier times out, participants do nothing. We rely on fact that the timeout happened because of a participant leaving. But if it timed out for any other reason, we may end up in a stuck state.
> So to cover this unknown we will add an explicit call to doOnProcessorChange for the leader.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)