Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1331E106B3 for ; Thu, 11 Jul 2013 16:32:43 +0000 (UTC) Received: (qmail 65974 invoked by uid 500); 11 Jul 2013 16:32:40 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 65876 invoked by uid 500); 11 Jul 2013 16:32:40 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 65861 invoked by uid 99); 11 Jul 2013 16:32:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jul 2013 16:32:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.215.41 as permitted sender) Received: from [209.85.215.41] (HELO mail-la0-f41.google.com) (209.85.215.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jul 2013 16:32:33 +0000 Received: by mail-la0-f41.google.com with SMTP id fn20so7038371lab.28 for ; Thu, 11 Jul 2013 09:32:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=s+cNZVMGLlr0TTZOiJrJ4gZrJHrBSVdAx1oeG1bOgIQ=; b=Do/HmgXWPZuEOaV8+S4LAS22rJOaiVw9AdjUAvCGtXWqYmgPRDQFr7LUiUesxlNaSz fP5E5EKc/zx/VuFQDH5eIXzNFNPqFL0syksMU1v8uzPLRaYa/WDrtGOA5Y+j8Vc9HCnV q4F1vQDFpVoTx/GN9EidegjVQUgn78RLuqJLYly2MFK5Ls9WBObt6GK5+BFu/SuOTo+A M3RaOBpDTNgyBEaXHLBA1QuwPfu109TmE96Y6QIZBM3AMD/70l0eoHCeyR8jZI3zyccO QTF2OIG6w2vdYgP8atdoBVhIig77CgVwlkBfgczWvWgI+0akdZpZ5xNEpC2gGNf8RtTh G7Aw== MIME-Version: 1.0 X-Received: by 10.112.164.164 with SMTP id yr4mr17559559lbb.88.1373560332203; Thu, 11 Jul 2013 09:32:12 -0700 (PDT) Received: by 10.112.141.5 with HTTP; Thu, 11 Jul 2013 09:32:12 -0700 (PDT) In-Reply-To: References: Date: Thu, 11 Jul 2013 09:32:12 -0700 Message-ID: Subject: Re: hbase.client.scanner.caching - default 1, not 100 From: Ted Yu To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=001a1133cb2cadbbf204e13eef98 X-Virus-Checked: Checked by ClamAV on apache.org --001a1133cb2cadbbf204e13eef98 Content-Type: text/plain; charset=ISO-8859-1 For 0.94, the following should be referenced: http://hbase.apache.org/0.94/book.html I searched for hbase.client.scanner.caching In section 2.3.1, you would see that its value is 1. Cheers On Thu, Jul 11, 2013 at 9:28 AM, Patrick Schless wrote: > In 0.94 I noticed (in the "Job File") my job VerifyRep job was running with > hbase.client.scanner.caching set to 1, even though the hbase docs [1] say > it defaults to 100. I didn't have that property being set in any of my > configs. I added the properties to hbase-site.xml (set to 100), and now > that job runs with 100, as expected. Is it possible that that docs are > wrong? > > [1] http://hbase.apache.org/book/config.files.html > --001a1133cb2cadbbf204e13eef98--