Return-Path: 
 <hbase-dev-return-10925-apmail-hadoop-hbase-dev-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org
Received: (qmail 33646 invoked from network); 15 Jun 2009 16:39:03 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 15 Jun 2009 16:39:03 -0000
Received: (qmail 8621 invoked by uid 500); 15 Jun 2009 16:39:14 -0000
Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org
Received: (qmail 8580 invoked by uid 500); 15 Jun 2009 16:39:14 -0000
Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hbase-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hbase-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hbase-dev@hadoop.apache.org>
List-Id: <hbase-dev.hadoop.apache.org>
Reply-To: hbase-dev@hadoop.apache.org
Delivered-To: mailing list hbase-dev@hadoop.apache.org
Received: (qmail 8570 invoked by uid 99); 15 Jun 2009 16:39:14 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jun 2009 16:39:14 +0000
X-ASF-Spam-Status: No, hits=2.2 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com
 designates 74.125.92.27 as permitted sender)
Received: from [74.125.92.27] (HELO qw-out-2122.google.com) (74.125.92.27)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jun 2009 16:39:05 +0000
Received: by qw-out-2122.google.com with SMTP id 3so1993561qwe.35
        for <hbase-dev@hadoop.apache.org>;
 Mon, 15 Jun 2009 09:38:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:sender:received:in-reply-to
         :references:date:x-google-sender-auth:message-id:subject:from:to
         :content-type;
        bh=YdRYGIqRv+qXhMHbBwH7Cp3Fp3r2ch4TsA16j5Ax9Tk=;
        b=UO5TBQOry9GC8EqOCdkdcos2eFUz5pmJscVBF12Z9vggqY1Aa5USHKbSNSTy8H2jpM
         ivSmZjbAaB6QQMC+loWKduxEUPepkyWwbhm1VVBnO+UQeetxSAfh1DtjSviwRalygHum
         +4+e6VUYgqlhs6Hz4t0nOtfgKfw8Sjc8uHxNs=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=X6uxhvbryTKwlOwyKTU6Wo2mjT49exY5+/Hntc5Pfxnk4fXppHXYEhePCMFQwRVf5/
         qcW9S8ZxEAJzdVSY/hTz2MkNFHQzbHLvmCXymfV5BFgK6Tsw+Pqig6xAVnMP5bnomH6z
         ELjjVdeQYVUz158nyiGA2hbbgD5Q9BbhCf7sk=
MIME-Version: 1.0
Sender: saint.ack@gmail.com
Received: by 10.229.96.13 with SMTP id f13mr1401228qcn.36.1245083924165; Mon,
	15 Jun 2009 09:38:44 -0700 (PDT)
In-Reply-To: <985454.1411245070506999.JavaMail.irfan@damascus>
References: <13361482.1391245070416545.JavaMail.irfan@damascus>
	 <985454.1411245070506999.JavaMail.irfan@damascus>
Date: Mon, 15 Jun 2009 09:38:44 -0700
X-Google-Sender-Auth: db62e2c6973b1b9c
Message-ID: <7c962aed0906150938v3a2c746bl7e5b8ed2f775b9ab@mail.gmail.com>
Subject: Re: new API method HTable.incrementColumnValue hangs
From: stack <stack@duboce.net>
To: hbase-dev@hadoop.apache.org
Content-Type: multipart/alternative; boundary=00163683248203f544046c65b122
X-Virus-Checked: Checked by ClamAV on apache.org

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

On Mon, Jun 15, 2009 at 5:55 AM, Irfan Mohammed <irfan.ma@gmail.com> wrote:

> using the hbase from the trunk on ubuntu 9.04
>
> irfan@damascus:~$ hbase shell
> HBase Shell; enter 'help<RETURN>' for list of supported commands.
> Version: 0.20.0-dev, r784503, Sun Jun 14 15:36:01 EDT 2009
>
> Whenever I use the new API call [HTable.incrementColumnValue], the process
> hangs. If I kill the process and later try to access the table records
> anywhere including "hbase shell" etc., even that process hangs.
>
> 1. "stop-hbase.sh" hangs as well and I have to kill the hbase processes



Please make a thread dump -- "% kill -QUIT PID" -- and pastebin what you
see.  I'd be interested in seeing why hbase won't go down.


>
> 2. restart the hbase using "start-hbase.sh"
> 3. hbase shell> count 't1' ---> throws an error that the table if offline
> 4. so had to enable 't1' and then work with the table.
>

....


Going by above, maybe something else is up in your hbase cluster?

Maybe, ensure all is well before you run your code by doing a few operations
with the shell on initial startup?

Your code doesn't have obvious errors on a quick glance.

Ensure your cluster is healthy before you run your own code, I'd suggest.

St.Ack

--00163683248203f544046c65b122--