Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of germoglio@gmail.com
 designates 74.125.44.28 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=FiNk8gJv8NkSWacihCzGPn8V4AmIZ3uBBOK4kBUTWi9BhVhSGoNblQNnPlUyLCNL89
         mo0cOzjQp0xF+HNxW3yK59Us/oC31nG/gSsjORF+UayQBWSY3RaOiCtf2fUjt1UgUNtW
         S0YjytqHPsP/UzxfOXlcUYg7MQVYNs/9w8l/w=
MIME-Version: 1.0
In-Reply-To: <78568af10905091636r5d2607d8s9e7eeee7e56a9994@mail.gmail.com>
References: <29bed2720905081629r6d50a895g87304b05f5a0a4fa@mail.gmail.com>
	<78568af10905081651v4a2b72f1t68bf4fafed9b6189@mail.gmail.com>
	<29bed2720905081857v4dd4bb7ek7bba524401415eba@mail.gmail.com>
	<78568af10905081935g7afde413s7fda529b1ef7bad4@mail.gmail.com>
	<29bed2720905091546q9f8d988t280547775ab9144f@mail.gmail.com>
	<78568af10905091554i7f560ac3n5bbdcc53fa436207@mail.gmail.com>
	<29bed2720905091618s6519bad8kac7fd32a4d9816a3@mail.gmail.com>
	<78568af10905091636r5d2607d8s9e7eeee7e56a9994@mail.gmail.com>
From: Guilherme Germoglio <germoglio@gmail.com>
Date: Sat, 9 May 2009 20:44:28 -0300
Message-ID: <29bed2720905091644q670751f3rb64aa76741f32c2@mail.gmail.com>
Subject: Re: Problems when executing many (?) HTable.lockRow()
To: hbase-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=001e680f17b09ed422046983548d

--001e680f17b09ed422046983548d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

maybe you've just spotted the problem! I've raised
hbase.regionserver.handler.count to 100 and the threads are now executing
much faster! When 20 are running, they take about 80~90 ms each.

On Sat, May 9, 2009 at 8:36 PM, Ryan Rawson <ryanobjc@gmail.com> wrote:

> if we had a compare and set operation would this help you?
>
> Another thing, normally hbase regionserver only runs 10 ipc handler
> threads... I'm not sure how relevant or important this is yet. Holding a
> row
> open should not tie up an ipc thread though.
>
> On May 9, 2009 4:19 PM, "Guilherme Germoglio" <germoglio@gmail.com> wrote:
>
> Hey Ryan,
>
> Thank for such a quick response!
>
> The log is here: http://germoglio.googlepages.com/log.zip Unfortunately, I
> wasn't running with debug on. I'll do it tomorrow in order to get more data
> (Will I be able to find how to turn on debug in the mailing list archives
> or
> in hbase wiki?). Also, you will notice that the log is only from the master
> server. The reason for this is that I'm running on the pseudodistributed
> mode and the region server log has only one message "2009-05-09
> 19:04:26,242
> WARN org.apache.hadoop.hbase.regionserver.HRegionServer: Not starting a
> distinct region server because hbase.master is set to 'local' mode".
>
> Thank you for the advice. I understand that a simple put doesn't make sense
> to lock a row. However, I'm just considering the performance of it. If the
> put operation into a single row (which I think is the fastest operation)
> isn't fast enough for my project, I'll not even try what I'm really
> intending to do, which is atomically getting a value, modifying it (not
> necessarily incrementing it), and then putting it back to the table.
>
> I wasn't expecting great performance either, but is it ok to execute a
> single put into a locked row in 5~10 minutes?
>
> On Sat, May 9, 2009 at 7:54 PM, Ryan Rawson <ryanobjc@gmail.com> wrote: >
> Hey Guilherme, > > We'd ...
> --
>
> Guilherme msn: guigermoglio@hotmail.com homepage:
> http://germoglio.googlepages.com
>


-- 
Guilherme

msn: guigermoglio@hotmail.com
homepage: http://germoglio.googlepages.com

--001e680f17b09ed422046983548d--