[jira] [Updated] (SAMZA-1385) Coordination utils in LocalApplicationRunner uses same Zk node as ZkJobCoordinatorFactory for leader election

["Bharath Kumarasubramanian (JIRA)" <ji...@apache.org>]

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

Bharath Kumarasubramanian updated SAMZA-1385:
---------------------------------------------
    Summary: Coordination utils in LocalApplicationRunner uses same Zk node as ZkJobCoordinatorFactory for leader election  (was: Coordination utils in LocalApplicationRunner uses same Zk path as ZkJobCoordinatorFactory for leader election)

> Coordination utils in LocalApplicationRunner uses same Zk node 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 that involve creating intermediate stream, a single process waits for itself to become a leader during job coordination phase if it has already acquired leadership during stream creation phase.
> The reason for this starvation is due to the fact that both these leader election use the same zookeeper path. We need to separate use separate nodes for leader election for job model creation & stream creation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)