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 95611175AE for ; Wed, 22 Apr 2015 01:32:59 +0000 (UTC) Received: (qmail 36615 invoked by uid 500); 22 Apr 2015 01:32:59 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 36571 invoked by uid 500); 22 Apr 2015 01:32:59 -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 36416 invoked by uid 99); 22 Apr 2015 01:32:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Apr 2015 01:32:59 +0000 Date: Wed, 22 Apr 2015 01:32:59 +0000 (UTC) From: "Jonathan Lawlor (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-13527) The default value for hbase.client.scanner.max.result.size is never actually set on Scans 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-13527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Lawlor updated HBASE-13527: ------------------------------------ Status: Patch Available (was: Open) > The default value for hbase.client.scanner.max.result.size is never actually set on Scans > ----------------------------------------------------------------------------------------- > > Key: HBASE-13527 > URL: https://issues.apache.org/jira/browse/HBASE-13527 > Project: HBase > Issue Type: Bug > Affects Versions: 0.98.12, 1.0.0, 2.0.0, 1.1.0, 1.2.0 > Reporter: Jonathan Lawlor > Attachments: HBASE-13527-v1.patch > > > Now that max result size is driven from the client side like caching (HBASE-13362), we also need to set Scan.maxResultSize to the default value of hbase.client.scanner.max.result.size which is never performed. I think this has gone unnoticed because the server used to read the configuration hbase.client.scanner.max.result.size for itself, but now we expect the serialized Scan sent from the client side to contain this information. Realistically this should have been set on the Scans even before HBASE-13362, it's surprising that it's not as the scanner code seems to indicate otherwise. > Ultimately, the end result is that, by default, scan RPC's are limited by hbase.server.scanner.max.result.size (note this is the new server side config not the client side config) which has a default value of 100 MB. The scan RPC's should instead be limited by hbase.client.scanner.max.result.size which has a default value of 2 MB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)