[
https://issues.apache.org/jira/browse/SAMZA-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanil Jain updated SAMZA-2402:
------------------------------
Description:
On job restarts, there might be already pending container placement requests
from the previous deployment. Since a new deploy can potentially change the job
state (some containers might lose affinity), we should not allow pending
control actions to be taken from the previous deployment
Also even if the metastore is eventually consistent, duplicate actions
delivered to the metastore should be only taken once
was:On job restarts, there might be already pending container placement
requests from the previous deployment. Since a new deploy can potentially
change the job state (some containers might lose affinity), we should not allow
pending control actions to be taken from previous deployment
> Disallow pending Container Placement actions in metastore on job restarts
> -------------------------------------------------------------------------
>
> Key: SAMZA-2402
> URL: https://issues.apache.org/jira/browse/SAMZA-2402
> Project: Samza
> Issue Type: New Feature
> Reporter: Sanil Jain
> Assignee: Sanil Jain
> Priority: Major
>
> On job restarts, there might be already pending container placement requests
> from the previous deployment. Since a new deploy can potentially change the
> job state (some containers might lose affinity), we should not allow pending
> control actions to be taken from the previous deployment
> Also even if the metastore is eventually consistent, duplicate actions
> delivered to the metastore should be only taken once
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
