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 091CE10FE9 for ; Tue, 1 Oct 2013 03:27:41 +0000 (UTC) Received: (qmail 65501 invoked by uid 500); 1 Oct 2013 03:27:40 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 65468 invoked by uid 500); 1 Oct 2013 03:27:38 -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 65460 invoked by uid 99); 1 Oct 2013 03:27:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Oct 2013 03:27:36 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of josh.elser@gmail.com designates 209.85.216.180 as permitted sender) Received: from [209.85.216.180] (HELO mail-qc0-f180.google.com) (209.85.216.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Oct 2013 03:27:30 +0000 Received: by mail-qc0-f180.google.com with SMTP id p19so4239887qcv.25 for ; Mon, 30 Sep 2013 20:27:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=66dAjd8x9ok+WeIel4U/o5RcPm+9PTQqxO4f0b+TRhM=; b=zpPoPZ4gSbCEE+l7s/AXQrhossyd7sorqafer9rlN7NtSnKaoQst50dCBOFfdjAfg0 VWK3Yz3ajQzWSneOvTDQgDgfmb28M0HeuLbDigpfA9ty/V3OX3hQSXkR6Zp8teGlLiVO iPxVP10LEYqoXOQFms2UWrEQyF71riGnOkWXibRdrY8lo5Gdmtjq+8yeou2uvfC9xIzT BrwRGcW1eYvq9LbHVk5A9dM/aN0Hmu8jDEJnSnYXRGCdr48DKQcwkQ3ibEX47Z7KVxh6 ofumAMYlYsUNQR2NJZEMd944a4Fbz9w+dPLO/ckFdyHlZHuB8xFaczc5Bhpb3bGA3guP YBEw== X-Received: by 10.224.136.136 with SMTP id r8mr18154341qat.37.1380598029656; Mon, 30 Sep 2013 20:27:09 -0700 (PDT) Received: from [192.168.2.210] (pool-72-81-136-94.bltmmd.fios.verizon.net. [72.81.136.94]) by mx.google.com with ESMTPSA id a2sm7792940qek.7.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 30 Sep 2013 20:27:08 -0700 (PDT) Message-ID: <524A4110.8070203@gmail.com> Date: Mon, 30 Sep 2013 23:27:12 -0400 From: Josh Elser User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130825 Thunderbird/17.0.8 MIME-Version: 1.0 To: user@accumulo.apache.org Subject: Re: Merge Tablets [SEC=UNOFFICIAL] References: <24070BEF0A3F684489AA943FD3439EF20586FA060E@CARRXM06.drn.mil.au> In-Reply-To: <24070BEF0A3F684489AA943FD3439EF20586FA060E@CARRXM06.drn.mil.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Matt, You interpreted the prompt correctly. That was added as a failsafe to keep you from merging your entire table into one tablet. The merge command doesn't take into account the split threshold, it simply merges all tablets specified by the rows you provide (or entire table) and merge them into one tablet. In other words, the configured table.split.threshold you have defined won't work as you expect. If you know how many tablets you want this table to have in the end (I believe the current recommendation is an upper-bound of ~200 tablets per tabletserver), you can use the current splits and some shell magic to create a script that you can pass the shell that will merge series of tablets together. e.g. merge -t table -b 1 -e 3 merge -t table -b 4 -e 6 merge -t table -b 7 -e 9 etc. - Josh On 09/30/2013 11:17 PM, Dickson, Matt MR wrote: > > *UNOFFICIAL* > > I have a table with 125K tablets and would like to merge the smaller > tablets together. The documentation states; > > Merging away small tablets works on one section at a time. If your > table contains many sections of small split points, or you are > attempting to change the split size of the entire table, it will be > faster to set the split point and merge the entire table: > > Based on this I went to run *'merge -t /tablename/'* on a table with > table.split.threshold set to 1G and was prompted to confirm if I > wanted to merge the entire table into a single tablet. > > I had thought Accumulo would find small tablets and merge these upto a > size of 1G, rather than attempt to create a single tablet. Am Ir > using the wrong command for this or misinterpreting the prompt? > > Thanks in advance, > > Matt >