You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Jake Maes (JIRA)" <ji...@apache.org> on 2018/01/12 19:27:05 UTC

[jira] [Updated] (SAMZA-1113) Implement startup and shutdown sequence of jobs in ZK environment

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

Jake Maes updated SAMZA-1113:
-----------------------------
    Fix Version/s:     (was: 0.14.0)
                   0.15.0

> Implement startup and shutdown sequence of jobs in ZK environment
> -----------------------------------------------------------------
>
>                 Key: SAMZA-1113
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1113
>             Project: Samza
>          Issue Type: Sub-task
>            Reporter: Navina Ramesh
>            Assignee: Navina Ramesh
>             Fix For: 0.15.0
>
>         Attachments: SAMZA-1113-0.md, SAMZA-1113-0.pdf
>
>
> Problem that we need to solve is: Do we need multiple job attempts in the ZK tree? If yes, who creates the persistent subtrees? There is no leader until the ZK trees are setup.
> In the initial prototype, the first processor instance creates the ZK hierarchy. If we were to support multiple job attempts, then we need different ZK trees for each attempt. How do all the processors within a job know which the attempt ID to join?



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