[ 
https://issues.apache.org/jira/browse/HADOOP-10219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603251#comment-16603251
 ] 

Hudson commented on HADOOP-10219:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14871 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/14871/])
HADOOP-10219. ipc.Client.setupIOstreams() needs to check for (stevel: rev 
9e96ac666d783376a8cdea9c3cc84098c5bdcb56)
* (edit) 
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ipc/TestIPC.java
* (edit) 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Client.java


> ipc.Client.setupIOstreams() needs to check for ClientCache.stopClient 
> requested shutdowns 
> ------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-10219
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10219
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 2.2.0, 2.6.0
>            Reporter: Steve Loughran
>            Assignee: Kihwal Lee
>            Priority: Major
>             Fix For: 3.2.0, 3.1.2
>
>         Attachments: HADOOP-10219.patch, HADOOP-10219.v1.patch, 
> HADOOP-10219.v2.patch, HADOOP-10219.v3.patch, HADOOP-10219.v4.patch
>
>
> When {{ClientCache.stopClient()}} is called to stop the IPC client, if the 
> client
>  is blocked spinning due to a connectivity problem, it does not exit until 
> the policy has timed out -so the stopClient() operation can hang for an 
> extended period of time.
> This can surface in the shutdown hook of FileSystem.cache.closeAll()
> Also, Client.stop() is for used in NN switch from Standby to Active, and can 
> therefore have very bad consequences and cause downtime.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to