You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jian He (JIRA)" <ji...@apache.org> on 2016/12/14 00:16:58 UTC

[jira] [Created] (YARN-5999) AMRMClientAsync will stop if any exceptions thrown on allocate call

Jian He created YARN-5999:
-----------------------------

             Summary: AMRMClientAsync will stop if any exceptions thrown on allocate call 
                 Key: YARN-5999
                 URL: https://issues.apache.org/jira/browse/YARN-5999
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Jian He


Currently, for any exceptions thrown on the allocate call of AMRMClientAsync,  it will stop both heartbeat thread and the callback handler thread, leaving AMRMClient in an unusable state.  Caller has to instantiate a new AMRMClient. 
IMO, the threads should keep on running, it should be up to the caller whether to stop the AMRMClient or not.

{code}
          try {
            response = client.allocate(progress);
          } catch (ApplicationAttemptNotFoundException e) {
            handler.onShutdownRequest();
            LOG.info("Shutdown requested. Stopping callback.");
            return;
          } catch (Throwable ex) {
            LOG.error("Exception on heartbeat", ex);
            savedException = ex;
            // interrupt handler thread in case it waiting on the queue
            handlerThread.interrupt();
            return;
          }
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org