hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14034) Allow ipc layer exceptions to selectively close connections
Date Thu, 09 Feb 2017 17:04:42 GMT

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

Kihwal Lee commented on HADOOP-14034:

It is very nice of you to fix prior unresolved merge conflict that got checked in.

-<<<<<<< HEAD
-     * Process an RPC Request - handle connection setup and decoding of
-     * request into a Call
      * Process one RPC Request from buffer read from socket stream 
      *  - decode rpc in a rpc-Call
      *  - handle out-of-band RPC requests such as the initial connectionContext
@@ -2264,17 +2255,16 @@ private void unwrapPacketAndProcessRpcs(byte[] inBuf)
      * if SASL then SASL has been established and the buf we are passed
      * has been unwrapped from SASL.
->>>>>>> 3d94da1... HADOOP-11552. Allow handoff on the server side for
RPC requests. Contributed by Siddharth Seth
      * @param bb - contains the RPC request header and the rpc request

> 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
>         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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message