hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2870) Datanode.shutdown() and Namenode.stop() should close all rpc connections
Date Thu, 13 Mar 2008 11:29:46 GMT

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

Tom White commented on HADOOP-2870:
-----------------------------------

Just noticed that this change removed the public RPC.stopClient() method. It's still used
by DFSLocationsRoot in contrib. Should we add it back as a deprecated no-op? Or at least mark
this change as incompatible in the change log and fix contrib.

> Datanode.shutdown() and Namenode.stop() should close all rpc connections
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-2870
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2870
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.16.0
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.17.0
>
>         Attachments: closeConnection.patch, closeConnection1.patch, closeConnection2.patch,
closeConnection3.patch, closeConnection4.patch
>
>
> Currently this two cleanup methods do not close all existing rpc connections. If a mini
dfs cluster gets shutdown and then restarted as we do in TestFileCreation, RPCs in second
mini cluster reuse the unclosed connections opened in the first run but there is no server
running to serve the request. So the client get stuck waiting for the response forever if
client side timeout gets removed as suggested by hadoop-2811.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message