[
https://issues.apache.org/jira/browse/SLIDER-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Samel updated SLIDER-1066:
--------------------------------
Affects Version/s: Slider 0.90.2
> Make AM restart during upgrade option - e.g. via a option to upgrade command
> ----------------------------------------------------------------------------
>
> Key: SLIDER-1066
> URL: https://issues.apache.org/jira/browse/SLIDER-1066
> Project: Slider
> Issue Type: Improvement
> Affects Versions: Slider 0.80, Slider 0.90.2
> Reporter: Manoj Samel
>
> During "slider upgrade" command e.g. to add a new component; the slider AM
> itself restarts.
> One slide use case is deploy a service via slider and create a new component
> for every new user of service. New components are added via "slider upgrade"
> so existing components (i.e. users) are not impacted by down time. During
> each component upgrade the AM also restarts and all existing components have
> to know the new AM before they can heartbeat to it.
> Per discussions, the AM restart during upgrade is being done to pick up new
> Yarn parameters.
> However, in this use case, Hadoop cluster yarn parameters are not being
> changed; neither are parameters to any of the existing components. Thus the
> AM restart in this case seems to provide no benefit - though it brings a
> small risk that any issue in AM restart will shut down the entire application
> (i.e. impact all running users).
> An option should be provided during the upgrade to NOT do AM restart -
> allowing users of slider to have a choice.
> Filing the improvement Jira per discussion on d-list.
> Thanks,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
