[
https://issues.apache.org/jira/browse/HADOOP-10219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603447#comment-16603447
]
Íñigo Goiri commented on HADOOP-10219:
--------------------------------------
bq. closing as fixed; if you want this for branch-2: Re-open, submit a branch-2
patch & see how happy jenkins is
This applies cleanly to both branch-2 and branch-2.9.
Run tests on branch-2.9 and it looks good.
I'm cherry-picking the commit.
> 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-branch-2.000.patch, 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]
