Thank you Sumit.
On Sat, Mar 14, 2015 at 9:51 PM, Sumit Mohanty
wrote:
> This error is usually harmless - it happens when application is being
> stopped (slider stop cl1) and Slider Agents may still be heartbeating with
> the AppMaster.
>
>
> > impl.AMRMClientAsyncImpl - Interrupted while waiti
This error is usually harmless - it happens when application is being stopped
(slider stop cl1) and Slider Agents may still be heartbeating with the
AppMaster.
> impl.AMRMClientAsyncImpl - Interrupted while waiting for queue
> java.lang.InterruptedException
> at
> java.util.concurrent.l
Kishore:
Looks like logging was at INFO level.
Do you mind turning on DEBUG logging ?
Thanks
On Sat, Mar 14, 2015 at 7:39 AM, Krishna Kishore Bonagiri <
write2kish...@gmail.com> wrote:
> Hi Steve,
>
> This is what I see in the AM's log since the STOP command is issued. Even
> though it indicat
Hi Steve,
This is what I see in the AM's log since the STOP command is issued. Even
though it indicates that STOP command SUCCEEDED, I see that the stop
function in my python script is not getting executed. Does the exception at
the end of this log indicate something?
2015-03-14 07:24:01,202 [I
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 t
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 applica
