hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16752) Upgrading from 1.2 to 1.3 can lead to replication failures due to difference in RPC size limit
Date Thu, 20 Oct 2016 02:49:58 GMT

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

Hudson commented on HBASE-16752:

FAILURE: Integrated in Jenkins build HBase-1.4 #479 (See [https://builds.apache.org/job/HBase-1.4/479/])
HBASE-16752 Return error back to rpc client on exceeding rpc request (garyh: rev 33e89fa9cfd4036fe972ff892df957603ae25bbf)
* (add) hbase-client/src/main/java/org/apache/hadoop/hbase/exceptions/RequestTooBigException.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/exceptions/ClientExceptionsUtil.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java
* (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/AbstractTestIPC.java

> Upgrading from 1.2 to 1.3 can lead to replication failures due to difference in RPC size
> ----------------------------------------------------------------------------------------------
>                 Key: HBASE-16752
>                 URL: https://issues.apache.org/jira/browse/HBASE-16752
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication, rpc
>    Affects Versions: 2.0.0, 1.3.0
>            Reporter: Ashu Pachauri
>            Assignee: Ashu Pachauri
>             Fix For: 2.0.0, 1.3.0, 1.4.0
>         Attachments: HBASE-16752.V1.patch, HBASE-16752.V2.patch, HBASE-16752.addendum.patch
> In HBase 1.2, we don't limit size of a single RPC but in 1.3 we limit it by default to
256 MB.  This means that during upgrade scenarios (or when source is 1.2 peer is already on
1.3), it's possible to encounter a situation where we try to send an rpc with size greater
than 256 MB because we never unroll a WALEdit while sending replication traffic.
> RpcServer throws the underlying exception locally, but closes the connection with returning
the underlying error to the client, and client only sees a "Broken pipe" error.
> I am not sure what is the proper fix here (or if one is needed) to make sure this does
not happen, but we should return the underlying exception to the RpcClient, because without
it, it can be difficult to diagnose the problem, especially for someone new to HBase.

This message was sent by Atlassian JIRA

View raw message