You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Boris Shkolnik (JIRA)" <ji...@apache.org> on 2017/07/19 21:53:00 UTC
[jira] [Commented] (SAMZA-1302) Improve Zookeeper error handling
[ https://issues.apache.org/jira/browse/SAMZA-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093863#comment-16093863 ]
Boris Shkolnik commented on SAMZA-1302:
---------------------------------------
[~spvenkat] Please see if this can be resolved and the corresponding test in TesZkLocalApplicaitonRunner enabled back.
> Improve Zookeeper error handling
> ---------------------------------
>
> Key: SAMZA-1302
> URL: https://issues.apache.org/jira/browse/SAMZA-1302
> Project: Samza
> Issue Type: Bug
> Reporter: Shanthoosh Venkataraman
> Assignee: Shanthoosh Venkataraman
> Priority: Minor
> Fix For: 0.14.0, 0.13.1
>
>
> In samza standalone, Zookeeper is used for accomplishing the following.
> A) For storing and retrieving the job model.
> B) Leader election amongst available stream processors.
> C) Propagating job model expiry to stream processors.
> D) Barrier for job model version upgrade.
> ZooKeeper Exceptions from all of the above scenarios are not propagated back to LocalApplicationRunner.waitForFinish.
> Incase of exception, an application will wait indefinitely if it is not bubbled up correctly.
> Potentially could cause stalled processors and duplicate stream processors.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)