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

Bharath Kumarasubramanian updated SAMZA-1385:
---------------------------------------------
    Description: 
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.

  was:
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.


> 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 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)

Reply via email to