Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E9F9E10FDC for ; Sat, 6 Jun 2015 21:36:00 +0000 (UTC) Received: (qmail 17970 invoked by uid 500); 6 Jun 2015 21:36:00 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 17920 invoked by uid 500); 6 Jun 2015 21:36:00 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 17909 invoked by uid 99); 6 Jun 2015 21:36:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Jun 2015 21:36:00 +0000 Date: Sat, 6 Jun 2015 21:36:00 +0000 (UTC) From: "Dev Lakhani (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-13825) Get operations on large objects fail with protocol errors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-13825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575960#comment-14575960 ] Dev Lakhani commented on HBASE-13825: ------------------------------------- This probably needs to be configurable as a Hbase option as we cannot change client code. > Get operations on large objects fail with protocol errors > --------------------------------------------------------- > > Key: HBASE-13825 > URL: https://issues.apache.org/jira/browse/HBASE-13825 > Project: HBase > Issue Type: Bug > Affects Versions: 1.0.0, 1.0.1 > Reporter: Dev Lakhani > > When performing a get operation on a column family with more than 64MB of data, the operation fails with: > Caused by: Portable(java.io.IOException): Call to host:port failed on local exception: com.google.protobuf.InvalidProtocolBufferException: Protocol message was too large. May be malicious. Use CodedInputStream.setSizeLimit() to increase the size limit. > at org.apache.hadoop.hbase.ipc.RpcClient.wrapException(RpcClient.java:1481) > at org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1453) > at org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1653) > at org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1711) > at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.get(ClientProtos.java:27308) > at org.apache.hadoop.hbase.protobuf.ProtobufUtil.get(ProtobufUtil.java:1381) > at org.apache.hadoop.hbase.client.HTable$3.call(HTable.java:753) > at org.apache.hadoop.hbase.client.HTable$3.call(HTable.java:751) > at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:120) > at org.apache.hadoop.hbase.client.HTable.get(HTable.java:756) > at org.apache.hadoop.hbase.client.HTable.get(HTable.java:765) > at org.apache.hadoop.hbase.client.HTablePool$PooledHTable.get(HTablePool.java:395) > This may be related to https://issues.apache.org/jira/browse/HBASE-11747 but that issue is related to cluster status. > Scan and put operations on the same data work fine > Tested on a 1.0.0 cluster with both 1.0.1 and 1.0.0 clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)