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 91E6517E44 for ; Thu, 9 Apr 2015 03:34:13 +0000 (UTC) Received: (qmail 7298 invoked by uid 500); 9 Apr 2015 03:34:13 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 7238 invoked by uid 500); 9 Apr 2015 03:34:13 -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 7215 invoked by uid 99); 9 Apr 2015 03:34:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Apr 2015 03:34:13 +0000 Date: Thu, 9 Apr 2015 03:34:13 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-13362) set max result size from client only (like caching)? 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-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-13362: ---------------------------------- Attachment: 13362-master-v2.txt With hbase-defaults definition. > set max result size from client only (like caching)? > ---------------------------------------------------- > > Key: HBASE-13362 > URL: https://issues.apache.org/jira/browse/HBASE-13362 > Project: HBase > Issue Type: Brainstorming > Reporter: Lars Hofhansl > Assignee: Lars Hofhansl > Fix For: 2.0.0, 1.1.0, 0.98.13 > > Attachments: 13362-0.98.txt, 13362-master-v2.txt, 13362-master.txt > > > With the recent problems we've been seeing client/server result size mismatch, I was thinking: Why was this not a problem with scanner caching? > There are two reasons: > # number of rows is easy to calculate (and we did it correctly) > # caching is only controlled from the client, never set on the server alone > We did fix both #1 and #2 in HBASE-13262. > Still, I'd like to discuss the following: > * default the client sent max result size to 2mb > * remove any server only result sizing > * continue to use hbase.client.scanner.max.result.size but enforce it via the client only (as the name implies anyway). > Comments? Concerns? -- This message was sent by Atlassian JIRA (v6.3.4#6332)