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 1DB5FEB2F for ; Sat, 12 Jan 2013 15:40:02 +0000 (UTC) Received: (qmail 2105 invoked by uid 500); 12 Jan 2013 15:39:59 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 2010 invoked by uid 500); 12 Jan 2013 15:39:59 -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 1995 invoked by uid 99); 12 Jan 2013 15:39:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Jan 2013 15:39:59 +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 anoop.hbase@gmail.com designates 209.85.219.45 as permitted sender) Received: from [209.85.219.45] (HELO mail-oa0-f45.google.com) (209.85.219.45) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Jan 2013 15:39:51 +0000 Received: by mail-oa0-f45.google.com with SMTP id i18so2703636oag.4 for ; Sat, 12 Jan 2013 07:39:30 -0800 (PST) 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=AR3fnlgIac8wOG8KL9n/XdmifTlwGHbfOWLscsxXiK4=; b=ShMe6FK/RR21Ab9852jnF4wbH6WrUo0QDi05xIMly/RAxP4A/1d6El/Vc+xe66IvxT ocHr07exTgIiUAX6TXsB7+UFxa9QaHUO5JQ2OJNQ/Dndm04QRz62pb1L6RMQdXJ+COu4 73KqwaBOkO1iVdvzSfhVLNfFaBFophpLhUDJJ7/dT7RVC0h9QSHOJ9oZhwFMQPqWn/OE HRlnclrBrbPiMPdjwr0BxSBI/99nXj+ReO1Er8UQ9i8P4N1vEX3lybWWmbKqYVLPpuas V/fvWbjAEHXlAZTKjaHT6QtMYFUkJ7C9PSgDKGUwvwev7WoRh91rNONqCWQNxHf5MZ7E pVVw== MIME-Version: 1.0 Received: by 10.60.25.161 with SMTP id d1mr49035617oeg.16.1358005169910; Sat, 12 Jan 2013 07:39:29 -0800 (PST) Received: by 10.76.74.106 with HTTP; Sat, 12 Jan 2013 07:39:29 -0800 (PST) In-Reply-To: References: Date: Sat, 12 Jan 2013 21:09:29 +0530 Message-ID: Subject: Re: Increment operations in hbase From: Anoop John To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=e89a8ff1c2bec1750404d319374f X-Virus-Checked: Checked by ClamAV on apache.org --e89a8ff1c2bec1750404d319374f Content-Type: text/plain; charset=ISO-8859-1 Hi Can you check with using API HTable#batch()? Here you can batch a number of increments for many rows in just one RPC call. Might help you to reduce the net time taken. Good luck. -Anoop- On Sat, Jan 12, 2013 at 4:07 PM, kiran wrote: > Hi, > > My usecase is I need to increment 1 million rows with in 15 mins. I tried > two approaches but none of the yielded results. > > I have used HTable.increment, but is not getting completed in the specified > time. I tried multi-threading also but it is very costly. I have also > implemented get and put as other alternative, but that approach is also not > getting completed in 15 mins. > > Can I use any low level implementation like using "Store or HRegionServer" > to increment 1 million rows. I know the table splits, and region servers > serving them, and rows which fall into table splits. I suspect the major > concern as network I/O rather than processing with the above two > approaches. > > -- > Thank you > Kiran Sarvabhotla > > -----Even a correct decision is wrong when it is taken late > --e89a8ff1c2bec1750404d319374f--