Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-12213

Interrupted exception can occur when Client#stop is called

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.3.0
    • Fix Version/s: 2.8.0, 2.7.2, 3.0.0-alpha1
    • Component/s: None
    • Labels:
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      Its more of a nuisance then a bug, but nevertheless

      16:16:48,709 ERROR pool-1-thread-1 ipc.Client:195 - Interrupted while waiting for clientExecutorto stop
      java.lang.InterruptedException
      	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2072)
      	at java.util.concurrent.ThreadPoolExecutor.awaitTermination(ThreadPoolExecutor.java:1468)
      	at org.apache.hadoop.ipc.Client$ClientExecutorServiceFactory.unrefAndCleanup(Client.java:191)
      	at org.apache.hadoop.ipc.Client.stop(Client.java:1235)
      	at org.apache.hadoop.ipc.ClientCache.stopClient(ClientCache.java:100)
      	at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.close(ProtobufRpcEngine.java:251)
      	at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:626)
      	at org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.close(ApplicationClientProtocolPBClientImpl.java:112)
      	at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:621)
      	at org.apache.hadoop.io.retry.DefaultFailoverProxyProvider.close(DefaultFailoverProxyProvider.java:57)
      	at org.apache.hadoop.io.retry.RetryInvocationHandler.close(RetryInvocationHandler.java:206)
      	at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:626)
      	at org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStop(YarnClientImpl.java:124)
      	at org.apache.hadoop.service.AbstractService.stop(AbstractService.java:221)
      . . .
      

      It happens sporadically when stopping YarnClient.
      Looking at the code in Client's 'unrefAndCleanup' its not immediately obvious why and who throws the interrupt but in any event it should not be logged as ERROR. Probably a WARN with no stack trace.
      Also, for consistency and correctness you may want to Interrupt current thread as well.

        Attachments

        1. YARN-1965-v3.patch
          5 kB
          Kuhu Shukla
        2. YARN-1965-v2.patch
          5 kB
          Kuhu Shukla
        3. YARN-1965.patch
          5 kB
          Kuhu Shukla

          Activity

            People

            • Assignee:
              kshukla Kuhu Shukla
              Reporter:
              ozhurakousky Oleg Zhurakousky
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: