Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 21927 invoked from network); 17 Aug 2009 22:10:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Aug 2009 22:10:41 -0000 Received: (qmail 16582 invoked by uid 500); 17 Aug 2009 22:10:59 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 16523 invoked by uid 500); 17 Aug 2009 22:10:59 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 16513 invoked by uid 99); 17 Aug 2009 22:10:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2009 22:10:59 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates 74.125.92.27 as permitted sender) Received: from [74.125.92.27] (HELO qw-out-2122.google.com) (74.125.92.27) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2009 22:10:50 +0000 Received: by qw-out-2122.google.com with SMTP id 8so997655qwh.35 for ; Mon, 17 Aug 2009 15:10:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=P1NvUAxvTXcbF2qD6DoCi1MKJJusAp2LzkUSBfy1awA=; b=rHXrfJUDU5o3DWg09HSAVbrT8xKKag49gOyCgo03yWQZHwcmBOynDlvF4QJwNlvPtK KNmX6+zyc3997JtC8RYAsPd3jcZNpgq1sOqr9/2nv/fqzh+ixlFXYzHSyjPGk4teDr8/ R9ulXPh1dtj8rFpJOzmFaiLtEU/VO46w+h8gI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=HPY75CqIiA41+HOA9S+gLhrmMlbRAqD9PevSv21VVxWfHr9/J/XBNE6s5HyJ2VYzI7 1DkTzfv8GRjSMED/CXT+p3uD7wXREo2q/bzYxf3GbossDLgLTtNybPo2e3pEQNc2KZMt 7OxOnXZxtW1XzaJ8m97M6DohYZg435fAqQs+o= MIME-Version: 1.0 Sender: saint.ack@gmail.com Received: by 10.229.13.12 with SMTP id z12mr2279663qcz.102.1250547029361; Mon, 17 Aug 2009 15:10:29 -0700 (PDT) In-Reply-To: <4AB0C5D9593B434CB25AFEE43248EC99052F5183@SNV-EXVS05.ds.corp.yahoo.com> References: <4AB0C5D9593B434CB25AFEE43248EC99052F5183@SNV-EXVS05.ds.corp.yahoo.com> Date: Mon, 17 Aug 2009 15:10:29 -0700 X-Google-Sender-Auth: 39126530609f6607 Message-ID: <7c962aed0908171510u606c41fbq3d7d3543e2397fb0@mail.gmail.com> Subject: Re: memcache size configurable? From: stack To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016363ba21275c46004715dabeb X-Virus-Checked: Checked by ClamAV on apache.org --0016363ba21275c46004715dabeb Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit >From hbase-default.xml: hbase.hregion.memstore.flush.size 67108864 Memstore will be flushed to disk if size of the memstore exceeds this number of bytes. Value is checked by a thread that runs every hbase.server.thread.wakefrequency. Our memstore used to be called memcache. Why change it? St.Ack On Mon, Aug 17, 2009 at 2:42 PM, Adam Silberstein wrote: > Hi, > > The HBase architecture documentation says that the memcache size is > configurable. What does it default to? Is this an option I can set in > conf/hbase-site.xml? If so, does anybody know the syntax? > > > > Thanks, > > Adam > > > > --0016363ba21275c46004715dabeb--