Sorry, I think we've been creating confusion Sumit was referring to the fact that in the app-specific python scripts inside an app package, there's a stop operation which isn't implemented; the specific component instances currently get destroyed without warning when the slider AM hands back the containers to YARN.
The CLI "stop" operation is very much supported, and it should work. 1. The basic "slider stop cl1" operation is meant to find the running application and ask it to shut down. If this doesn't work, can we see (a) any stack trace on the client and (b) the tail end of the AM logs. 2. "slider stop cl1 --force" skips talking to the slider AM and talks to YARN direct. No matter what's going on inside the application, this will kill it. If it doesn't, there's something gone wrong on the client side about talking to YARN, or something very very wrong with the YARN system itself. Again, a client-side log will help us review this -steve > On 14 Mar 2015, at 07:09, Krishna Kishore Bonagiri <[email protected]> > wrote: > > Hi Sumit, > First of all thanks for the reply. > > What we have been trying is this kind of command from CLI. > slider stop cl1 > > So, as you are saying it doesn't yet work. But what is the other way to > stop the application? What do you mean by "The only time stop is called, > today, is when the application is stopped the Slider Agents call Stop"? > > Kishore > > On Sat, Mar 14, 2015 at 10:56 AM, Sumit Mohanty <[email protected]> > wrote: > >> Stop is not wired up to the Stop command from the CLI. The only time stop >> is called, today, is when the application is stopped the Slider Agents call >> Stop and wait for ~10 seconds before killing the processes. >> >> On Fri, Mar 13, 2015 at 8:05 PM, Krishna Kishore Bonagiri < >> [email protected]> wrote: >> >>> Hi, >>> >>> We are using Apache Slider 0.60 and implemented the management >> operations >>> start, status, stop, etc. in python script. Everything else is working >> but >>> the stop function is not getting invoked when the container is stopped. >> Is >>> this a known issue already? or is there any trick to make it work? >>> >>> >>> Thanks, >>> Kishore >>> >> >> >> >> -- >> thanks >> Sumit >>
