You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Bharath Kumarasubramanian (JIRA)" <ji...@apache.org> on 2017/08/11 22:43:00 UTC

[jira] [Updated] (SAMZA-1385) Fix coordination issues during stream creation in LocalApplicationRunner

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

Bharath Kumarasubramanian updated SAMZA-1385:
---------------------------------------------
    Summary: Fix coordination issues during stream creation in LocalApplicationRunner  (was: Coordination utils in LocalApplicationRunner uses same Zk node as ZkJobCoordinatorFactory for leader election)

> Fix coordination issues during stream creation in LocalApplicationRunner
> ------------------------------------------------------------------------
>
>                 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
>
>
> Bug fixes related to coordination logic around stream creation.
> 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 node. We need to use separate nodes for leader election for job model creation & stream creation.



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