[
https://issues.apache.org/jira/browse/SAMZA-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanil Jain updated SAMZA-2373:
------------------------------
Description:
*Design:* [SEP-22: Container Placements in
Samza|https://cwiki.apache.org/confluence/display/SAMZA/SEP-22%3A+Container+Placements+in+Samza]
*Changes:* : Following abilities are added as a part of this PR:
# Container placement service core functionality to the Job Coordinator code
# Ability to move containers to any / specific host for host affinity enabled
jobs
# Ability to move containers to any host only for host affinity disabled jobs
# Standby enabled jobs are not supported in the PR (will follow with the
stacked PR)
*Tests:*
# Unit tests are added to moc and end to end control action and behavior
# Manual testing matrix: [Container Placement Test
Plan|https://docs.google.com/spreadsheets/d/1v-fw0pHxKRobGkALDCno4FuPCsBhdepQ86vIGLHWu54/edit#gid=0]
*API Changes:*:
# This PR introduces behavior changes when a control action is active on job
coordinator in such scenario the JC will try to reserve resources for the
request, if it gets the resources it it attempts to stop the active container
then attempts to start on the allocated resouces
# All the state realted to control actions are mainted in memory in the JC,
followed up by reporting & cleanup as soon as the control action finished
*Upgrade Instructions:* None
*Usage Instructions:* The ability to access these apis will be added as a part
of follow up PR
*RB:* [https://github.com/apache/samza/pull/1219]
was:
*Design:* [SEP-22: Container Placements in
Samza|https://cwiki.apache.org/confluence/display/SAMZA/SEP-22%3A+Container+Placements+in+Samza]
*Changes:* : Following abilities are added as a part of this PR:
# Container placement service core functionality to the Job Coordinator code
# Ability to move containers to any / specific host for host affinity enabled
jobs
# Ability to move containers to any host only for host affinity disabled jobs
# Standby enabled jobs are not supported in the PR (will follow with the
stacked PR)
*Tests:*
# Unit tests are added to moc and end to end control action and behavior
# Manual testing matrix: [Container Placement Test
Plan|https://docs.google.com/spreadsheets/d/1v-fw0pHxKRobGkALDCno4FuPCsBhdepQ86vIGLHWu54/edit#gid=0]
*API Changes:*:
# This PR introduces behavior changes when a control action is active on job
coordinator in such scenario the JC will try to reserve resources for the
request, if it gets the resources it it attempts to stop the active container
then attempts to start on the allocated resouces
# All the state realted to control actions are mainted in memory in the JC,
followed up by reporting & cleanup as soon as the control action finished
*Upgrade Instructions:* None
*Usage Instructions:* The ability to access these apis will be added as a part
of follow up PR
> Container Placements API for container move and restart
> --------------------------------------------------------
>
> Key: SAMZA-2373
> URL: https://issues.apache.org/jira/browse/SAMZA-2373
> Project: Samza
> Issue Type: New Feature
> Reporter: Sanil Jain
> Assignee: Sanil Jain
> Priority: Major
>
> *Design:* [SEP-22: Container Placements in
> Samza|https://cwiki.apache.org/confluence/display/SAMZA/SEP-22%3A+Container+Placements+in+Samza]
> *Changes:* : Following abilities are added as a part of this PR:
> # Container placement service core functionality to the Job Coordinator code
> # Ability to move containers to any / specific host for host affinity
> enabled jobs
> # Ability to move containers to any host only for host affinity disabled jobs
> # Standby enabled jobs are not supported in the PR (will follow with the
> stacked PR)
> *Tests:*
> # Unit tests are added to moc and end to end control action and behavior
> # Manual testing matrix: [Container Placement Test
> Plan|https://docs.google.com/spreadsheets/d/1v-fw0pHxKRobGkALDCno4FuPCsBhdepQ86vIGLHWu54/edit#gid=0]
> *API Changes:*:
> # This PR introduces behavior changes when a control action is active on job
> coordinator in such scenario the JC will try to reserve resources for the
> request, if it gets the resources it it attempts to stop the active container
> then attempts to start on the allocated resouces
> # All the state realted to control actions are mainted in memory in the JC,
> followed up by reporting & cleanup as soon as the control action finished
> *Upgrade Instructions:* None
> *Usage Instructions:* The ability to access these apis will be added as a
> part of follow up PR
> *RB:* [https://github.com/apache/samza/pull/1219]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
