Not sure if it matters, but on cluster where above failure happens, rack awareness is configured in core-site.xml. On other cluster where this behaviour is not seen, rack-awareness is not configured ... Saw https://issues.apache.org/jira/browse/SLIDER-905 so wanted to give more info ...
Manoj On Mon, Jan 4, 2016 at 4:51 PM, Manoj Samel <[email protected]> wrote: > Hi, > > Slider version .80 on secured cluster. > > I am seeing the pattern consistently > > 1. Create cluster with just slider AM. Works fine > 2. Slider upgrade to add 1 component. Works fine > 3. Slider upgrade to add 2nd component. After upgrade, the application > goes in FAILED state. > I start it manually using slider start > 4. Add 3rd component. Works fine > 5. Add 4th component. Application goes to FAILED state again. Repeats > again > > After addition of every 2nd component, the application fails and has to be > started again. > > The slider AM log does not contains any error etc. It only contains > following > > 2016-01-05 00:01:42,839 [Socket Reader #1 for port 1024] INFO > authorize.ServiceAuthorizationManager - Authorization successful for XYZ > (auth:TOKEN) for protocol=interface > org.apache.slider.server.appmaster.rpc.SliderClusterProtocolPB > 2016-01-05 00:01:42,846 [IPC Server handler 1 on 1024] INFO > rpc.SliderIPCService - AM Suicide with signal 1, message AM restarted for > application upgrade delay = 1000 > 2016-01-05 00:01:43,847 [AmExecutor-006] INFO util.ExitUtil - Halt with > status 1 Message: AM restarted for application upgrade > > Thanks, > > Manoj > >
