You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Navina Ramesh (JIRA)" <ji...@apache.org> on 2017/03/01 20:23:45 UTC

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

Navina Ramesh created SAMZA-1113:
------------------------------------

             Summary: 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


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.3.15#6346)