[
https://issues.apache.org/jira/browse/SAMZA-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312842#comment-15312842
]
Navina Ramesh commented on SAMZA-925:
-------------------------------------
Hi [~alex.buck10],
Sorry for the delay with this patch. I looked at it last week.
This JIRA doesn't have any description and I believe we were targeting
restarting containers without killing the application. In your patch, you are
writing a special message to the coordinator stream and the config manager
reacts by killing the current application and starting a new one. This was not
what was intended. When JobModel changes, the AM should coordinator killing all
containers and spawning new ones based on the new jobmodel. This way, the
application remains alive and only the partitions shuffle around.
Does that make sense? I will update the description in the JIRA and hopefully,
you can provide us a modified patch ! :)
Thanks!
Navina
> Explicit restart containers to pick up dynamic JobModel changes
> ---------------------------------------------------------------
>
> Key: SAMZA-925
> URL: https://issues.apache.org/jira/browse/SAMZA-925
> Project: Samza
> Issue Type: Sub-task
> Reporter: Yi Pan (Data Infrastructure)
> Assignee: Alex Buck
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
