[
https://issues.apache.org/jira/browse/HADOOP-14034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859861#comment-15859861
]
Hudson commented on HADOOP-14034:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11226 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11226/])
HADOOP-14034. Allow ipc layer exceptions to selectively close (kihwal: rev
b6bb99c18a772d2179d5cc6757cddf141e8d39c0)
* (edit)
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
* (edit)
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ipc/TestRPC.java
> Allow ipc layer exceptions to selectively close connections
> -----------------------------------------------------------
>
> Key: HADOOP-14034
> URL: https://issues.apache.org/jira/browse/HADOOP-14034
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: ipc
> Affects Versions: 2.7.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Fix For: 2.8.1, 3.0.0-alpha3
>
> Attachments: HADOOP-14034-branch-2.patch, HADOOP-14034-trunk.patch
>
>
> IPC layer exceptions generated in the readers are translated into fatal
> errors - resulting in connection closure. Ex. RetriableExceptions from call
> queue pushback.
> Always closing the connection degrades performance for all clients since a
> disconnected client will immediately reconnect on retry. Readers become
> overwhelmed servicing new connections and re-authentications from bad clients
> instead of servicing calls from good clients. The call queues run dry.
> Exceptions originating in the readers should be able to indicate if the
> exception is an error or fatal so connections can remain open.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
