In our application the "client" is actually one step of many in an application. If the "client" goes away entirely, that means the entire application has crashed or has been terminated somehow. Our application doesn't checkpoint state at this step, so the step will have to be restarted anyway. This doesn't break anything, it is just a waste to let it keep running. Thanks for clarifying the stateless nature of the client connection.
From: Vinod Kumar Vavilapalli [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 13, 2014 9:31 AM
To: [EMAIL PROTECTED]
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 though client is still alive etc.
Any more details on why this is desired?
On Jan 11, 2014, at 11:37 AM, John Lilley <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
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 client-AM connection) for that?
NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.