[
https://issues.apache.org/jira/browse/SAMZA-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937327#comment-15937327
]
Boris Shkolnik commented on SAMZA-1113:
---------------------------------------
GenerationId sounds like approach in general. Here are couple of open questions:
1. Does user have to generate this id manually, or it could be automated (based
on the version for example).
2. Since different teams deploy in different way - we may need to have a
plugable generator for it (yep, one more).
3. If same version restarts will reuse the same structure in ZK, we need to
introduce a cleanup on START. (we may want to preserve existing/previous
structure for debugging).
Shutdown:
We need to make sure that orderly shutdown of the JOB doesn't cause
reshuffling. This may be achieved by creating a flag in ZK.
I prefer this to relying on debounce time.
Do we need to support a case of single processor ONLY shutdown?
> 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.13.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.3.15#6346)
