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 A5ED2CAC8 for ; Wed, 26 Jun 2013 12:09:56 +0000 (UTC) Received: (qmail 5497 invoked by uid 500); 26 Jun 2013 12:09:55 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 5439 invoked by uid 500); 26 Jun 2013 12:09:49 -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 5421 invoked by uid 99); 26 Jun 2013 12:09:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jun 2013 12:09:47 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.128.179] (HELO mail-ve0-f179.google.com) (209.85.128.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jun 2013 12:09:41 +0000 Received: by mail-ve0-f179.google.com with SMTP id d10so11228113vea.24 for ; Wed, 26 Jun 2013 05:09:00 -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=rpNn8R3m0qteP6NtuaLqM1u93ybmnqSHjJvtX/moGhc=; b=cdwWuz6GHHYwSRbxN201zzkR4f8Aqxi6Eiu08vKTl6HbHuxkxgFZSCgVwDMZ3vgzIA HRfOSGTivY/k0lrBqVp5rWVJ76HBBuC/aAT39mmGNZJjVEQ7cc6u7wrXI2a/+hF3Vahp PsO55PtjTGMG/T91TP7leSTXNKsoCKVSlMQawnXVmD72IVzdlVnXb6GIpyhbKUR2Fe8/ xCcOCjh2iUH9eDJLO8tF1I8kP3tzJad5Xl9jf2WX9+saXU6GG44gcGdmUUJZ1XNnj3wc s63WRdoLuGi6KqklBumnUmRFTMtrJOAY8tXPBphli2EbTtQom4EAjhXgB/D+hIzlrP2s R71w== MIME-Version: 1.0 X-Received: by 10.58.97.199 with SMTP id ec7mr1545488veb.72.1372248540095; Wed, 26 Jun 2013 05:09:00 -0700 (PDT) Received: by 10.221.23.8 with HTTP; Wed, 26 Jun 2013 05:09:00 -0700 (PDT) In-Reply-To: <0A8F66C42F49E448A40E99946404EE5B768399BE07@aplesstar.dom1.jhuapl.edu> References: <0A8F66C42F49E448A40E99946404EE5B768399BE07@aplesstar.dom1.jhuapl.edu> Date: Wed, 26 Jun 2013 08:09:00 -0400 Message-ID: Subject: Re: Minor compaction occurring often with fairly long delays during ingest. From: Keith Turner To: user@accumulo.apache.org Content-Type: multipart/alternative; boundary=089e013a0696c6b61604e00d82e4 X-Gm-Message-State: ALoCoQkZ6afAUBsP3kF6dECyECvNBfGUR08lo/SkKKCiDnz1bUPitzru2FOcIoN2fEWIAGSPzhRv X-Virus-Checked: Checked by ClamAV on apache.org --089e013a0696c6b61604e00d82e4 Content-Type: text/plain; charset=ISO-8859-1 Its possible that you could be running into ACCUMULO-1062 [1], although I am thinking your large values may be at issue. Erics suggestion of having more tablets can help work around this issue, in addition to allowing more minc parallelism. [1] : https://issues.apache.org/jira/browse/ACCUMULO-1062 On Tue, Jun 25, 2013 at 7:06 PM, Hider, Sandy wrote: > I recently setup Accumulo 1.4.2 on a rack of boxes that each has 24 > processors and 43 GB of RAM. I set them up using the 3GB example templates > but then increased the max size of the Tserver and a few other components > to 5GB. > > Doing some initial tests importing roughly 7000 records, each record has > approximately 7 small fields and 1 large field holding data between 200Kb > to 1Mb in size. While ingesting I am seeing the server hold and start > minor compactions which seem to take quite a while after 2000-3000 records, > and then occurring again fairly frequently > > I am wondering what options I have to try and minimize the frequency of > minor compactions during ingest. What components memory sizes and config > properties would help me avoid this problem? If anyone has other ideas for > me to try and fix this please let me know. > > Thanks in advance, > > Sandy > > > > --089e013a0696c6b61604e00d82e4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Its possible that you could be running into ACC= UMULO-1062 [1], although I am thinking your large values may be at issue. = =A0Erics suggestion of having more tablets can help work around this issue,= in addition to allowing more minc parallelism.

[1] :=A0https://issues.apache.org/jira/browse/ACCUMULO-1062


On Tue, Jun= 25, 2013 at 7:06 PM, Hider, Sandy <Sandy.Hider@jhuapl.edu> wrote:
I recently setup Accumulo 1.4.2 on a rack of= boxes that each has 24 processors and 43 GB of RAM. =A0I set them up using= the 3GB example templates but then increased the max size of the Tserver a= nd a few other components to 5GB.

Doing some initial tests importing roughly 7000 records, each record has ap= proximately 7 small fields and 1 large field holding data between 200Kb to = 1Mb in size. =A0While ingesting I am seeing the server hold and start minor= compactions which seem to take quite a while after 2000-3000 records, and = then occurring again fairly frequently

I am wondering what options I have to try and minimize the frequency of min= or compactions during ingest. =A0 =A0What components memory sizes and confi= g properties would help me avoid this problem? =A0If anyone has other ideas= for me to try and fix this please let me know.

Thanks in advance,

Sandy




--089e013a0696c6b61604e00d82e4--