Flex isn't option for couple of reasons in above use case 1. For each new user, different parameters need to be passed when starting. New component allows control over component name and parameters 2. More importantly, when user is 'decomissioned', the component for that user should be stopped for good. This is achieved at present by naming each component after respective user and stopping that when user is gone.
Thanks, Manoj On Wed, Jan 13, 2016 at 10:11 AM, Steve Loughran <ste...@hortonworks.com> wrote: > you should just be flexing here > > > On 13 Jan 2016, at 09:19, Manoj Samel <manojsamelt...@gmail.com> wrote: > > > > Hi, > > > > In recent thread about existing components taking long time to heartbeat > > after upgrade; it was mentioned that "slider AM restarts itself to pick > up > > Yarn parameters" > > > > If the upgrade simply consist of starting a new component, is the AM > > restart still needed ? I.e. if the hadoop cluster configuration has not > > changed and the Yarn parameters in the slider applications have not > changed > > for any components and upgrade is being used just to start a new > component; > > is AM restart still needed ? > > > > The use case is for service running large number of components. When a > new > > user is enabled for service, a new component is started for that user. > > However, no changes are done for hadoop cluster or in the slider > > application configuration for any existing components. When large number > of > > users (i.e. components) are already running, AM restart means these > > existing components have to be informed of new AM and vice versa. > > > > In such cases, if AM restart is not needed, can it be avoided e.g. by > > having a new option in Upgrade command ? > > > > Thanks, > > > > Manoj > >
