You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Fred Ji (JIRA)" <ji...@apache.org> on 2017/08/09 21:33:00 UTC
[jira] [Updated] (SAMZA-1385) Coordination utils in
LocalApplicationRunner uses same Zk path as ZkJobCoordinatorFactory for
leader election
[ https://issues.apache.org/jira/browse/SAMZA-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Ji updated SAMZA-1385:
---------------------------
Affects Version/s: (was: 0.13.1)
> Coordination utils in LocalApplicationRunner uses same Zk path as ZkJobCoordinatorFactory for leader election
> -------------------------------------------------------------------------------------------------------------
>
> Key: SAMZA-1385
> URL: https://issues.apache.org/jira/browse/SAMZA-1385
> Project: Samza
> Issue Type: Bug
> Reporter: Bharath Kumarasubramanian
> Assignee: Bharath Kumarasubramanian
> Fix For: 0.13.1
>
>
> In case of applications which involves creating intermediate stream, we perform the leader election twice. once for coordination for stream creation and another for job coordination.
> We currently use the same zookeeper path for both of these and this results in two nodes for the same processor in zookeeper. As a result, the process goes into listener mode and stuck in job model generation phase.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)