hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashu Pachauri (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-16752) Upgrading from 1.2 to 1.3 can lead to replication failures due to difference in limits of RPC size
Date Mon, 03 Oct 2016 19:57:20 GMT
Ashu Pachauri created HBASE-16752:
-------------------------------------

             Summary: Upgrading from 1.2 to 1.3 can lead to replication failures due to difference
in limits of RPC size
                 Key: HBASE-16752
                 URL: https://issues.apache.org/jira/browse/HBASE-16752
             Project: HBase
          Issue Type: Bug
    Affects Versions: 1.3.0
            Reporter: Ashu Pachauri


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
(v6.3.4#6332)

Mime
View raw message