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 39F1C1748A for ; Thu, 5 Feb 2015 21:37:36 +0000 (UTC) Received: (qmail 3622 invoked by uid 500); 5 Feb 2015 21:37:36 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 3576 invoked by uid 500); 5 Feb 2015 21:37:36 -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 3562 invoked by uid 99); 5 Feb 2015 21:37:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Feb 2015 21:37:35 +0000 Date: Thu, 5 Feb 2015 21:37:35 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-12976) Set default value for hbase.client.scanner.max.result.size 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-12976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-12976: ---------------------------------- Fix Version/s: 1.1.0 > Set default value for hbase.client.scanner.max.result.size > ---------------------------------------------------------- > > Key: HBASE-12976 > URL: https://issues.apache.org/jira/browse/HBASE-12976 > Project: HBase > Issue Type: Bug > Reporter: Lars Hofhansl > Assignee: Lars Hofhansl > Fix For: 2.0.0, 1.0.1, 1.1.0, 0.94.27, 0.98.11 > > Attachments: 12976-v2.txt, 12976.txt > > > Setting scanner caching is somewhat of a black art. It's hard to estimate ahead of time how large the result set will be. > I propose we hbase.client.scanner.max.result.size to 2mb. That is good compromise between performance and buffer usage on typical networks (avoiding OOMs when the caching was chosen too high). > To an HTable client this is completely transparent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)