op.apache.org
Subject: Re: How to make AM terminate if client crashes?
The architecture is built around detachable clients. So, no, it doesn't happen
automatically. Even if we were to add that feature, it'd be fraught with edge
cases - network issues causing app-termination even thou
You would probably need to bake this into your own application. By default, a
client never should need to keep an open active connection with the RM. It
could keep an active connection with the AM ( application-specific code
required ) but it would then also have to handle failover to a differen
The architecture is built around detachable clients. So, no, it doesn't happen
automatically. Even if we were to add that feature, it'd be fraught with edge
cases - network issues causing app-termination even though client is still
alive etc.
Any more details on why this is desired?
+Vinod
On
You can set the maximum map and reduce attempts so that if a failure
occurred job gets failed and done.
On Sat, Jan 11, 2014 at 11:07 PM, John Lilley wrote:
> We have a YARN application that we want to automatically terminate if
> the YARN client disconnects or crashes. Is it possible to confi
We have a YARN application that we want to automatically terminate if the YARN
client disconnects or crashes. Is it possible to configure the YarnClient-RM
connection so that if the client terminates the RM automatically terminates the
AM? Or do we need to build our own logic (e.g. a direct cl
