[
https://issues.apache.org/jira/browse/SAMZA-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383746#comment-15383746
]
Alex Buck commented on SAMZA-925:
---------------------------------
Hi [~navina], Thanks very much for the feedback. I would like to have a look at
this again. Would you mind giving a little more background info on the best way
to do this?
Does the code for this functionality belong in the ConfigManager within
samza-autoscaling project as may previous patch was? Should this be the
component that polls the JobModel and then invokes asks the application master
to restart the containers when there has been a change in the JobModel?
Which APIs should be used for actually killing/starting the containers for a
particular application? Perhaps using
org.apache.hadoop.yarn.client.api.AMRMClient?
Cheers
Alex
> 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
>
> When JobModel changes, the Job Coordinator should trigger the AM to kill the
> existing containers and spawn new ones based on the JobModel update. This
> way, the application remains alive and only the partitions get re-distributed
> among the containers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
