Return-Path: X-Original-To: apmail-accumulo-user-archive@www.apache.org Delivered-To: apmail-accumulo-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 816C09DC2 for ; Wed, 8 Aug 2012 18:10:09 +0000 (UTC) Received: (qmail 15608 invoked by uid 500); 8 Aug 2012 18:10:09 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 15564 invoked by uid 500); 8 Aug 2012 18:10:09 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 15555 invoked by uid 99); 8 Aug 2012 18:10:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Aug 2012 18:10:09 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=FSL_RCVD_USER,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.212.41] (HELO mail-vb0-f41.google.com) (209.85.212.41) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Aug 2012 18:10:03 +0000 Received: by vbkv13 with SMTP id v13so1202063vbk.0 for ; Wed, 08 Aug 2012 11:09:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=EE0zsqU8T2olDa11pK4gKGMJG8bHXU+mYkC+aKA4I90=; b=HBB6q8/WSHV6m7WrlucM8Zgds3sk0AOzUabdPHd85C75uNMHW2kh4W/F1smGnXgtt8 Y0nDFoNKC/I1d4N6OmptHJC6m5WcOyElmOks39ffOsYYtYAeaVU8pirN+soaEN04c5TI w7weFNOiDy0JO2+ksEIFSn2klPdaCM0C5uTxfHoK0YN6nBudb+aGDAxJJ0/ALef39I0H 36pH1pbcpjxOwHzBmsgc6ZozLKvWQF0+NVleH8adlwcUDxVSASQzi+A4711H4LAw2lyx TC+4QesI87uAvvqYCFbHEJXk2UV9DOicGZ+f0h6I70psgVO5MwbC5OOU+LUeO9zjkpxo pVCg== MIME-Version: 1.0 Received: by 10.52.70.137 with SMTP id m9mr12705035vdu.49.1344449382313; Wed, 08 Aug 2012 11:09:42 -0700 (PDT) Received: by 10.59.8.5 with HTTP; Wed, 8 Aug 2012 11:09:42 -0700 (PDT) In-Reply-To: <97EB0FF1279CC5428640A3FB61B10BD602D47F9B@mx1.Comcept.L-3Com.com> References: <97EB0FF1279CC5428640A3FB61B10BD602D47F9B@mx1.Comcept.L-3Com.com> Date: Wed, 8 Aug 2012 14:09:42 -0400 Message-ID: Subject: Re: Time delay question From: Keith Turner To: user@accumulo.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlx6UWmIs17qF581TXY3FA17lohzIf35oNTGJNKq3Xpy1MRJIpeozc/8K2/TEI/ZeWS0ysF Once the batch writer flushes, the data is available for read by the batch scanner. On the server side data is read from memory and files. On Wed, Aug 8, 2012 at 1:53 PM, wrote: > I have a set of actors that are doing batchWriters and another set doing > batchScanner(s) and I'm getting questions from my users about the time > delay between them. So my question is, what are all the tunable > parameters between writes and reads? > > Do I have the following facts correct? > > BatchWriters have a time value for flushing to memory cache > Minor compaction has its time frequency for flushing to WALogs > Major compaction has its time frequency for flushing to disc > > So where all does a batchScanner get its data from? > > Any/all help is appreciated. > > > Bob Thorman > Engineering Fellow > L-3 Communications, ComCept > 1700 Science Place > Rockwall, TX 75032 > (972) 772-7501 work > Bob.Thorman@ncct.af.smil.mil > rdthorm@nsa.ic.gov > >