Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of eclark@stumbleupon.com
 designates 74.125.82.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAOT3TWr-m9Lfqbz+Qbmhhwaj-KS0f0q4aW0ZXaaZS3WcA-qm7A@mail.gmail.com>
References: 
 <CAOT3TWr-m9Lfqbz+Qbmhhwaj-KS0f0q4aW0ZXaaZS3WcA-qm7A@mail.gmail.com>
Date: Mon, 23 Jul 2012 15:54:58 -0700
Message-ID: 
 <CAKYwJ9wuPrgjJSzMcBU21Svud_X1Zu0WW4ymN8_w54suc9ZGog@mail.gmail.com>
Subject: Re: Insert blocked
From: Elliott Clark <eclark@stumbleupon.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=bcaec53d588791e0a904c58722a7

--bcaec53d588791e0a904c58722a7
Content-Type: text/plain; charset=ISO-8859-1

HTable is not thread safe[1]. It's better to use HTablePool if you want to
share things across multiple threads.[2]

1 http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/HTable.html
2
http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/HTablePool.html

On Mon, Jul 23, 2012 at 3:48 PM, Mohit Anchlia <mohitanchlia@gmail.com>wrote:

> I am writing a stress tool to test my specific use case. In my current
> implementation HTable is a global static variable that I initialize just
> once and use it accross multiple threads. Is this ok?
>
> My row key consists of (timestamp - (timestamp % 1000)) and cols are
> counters. What I am seeing is that when I run my test after first row is
> created the application just hangs. I just wanted to check if there are
> obvious things that I should watch out for.
>
> I am currently testing few threads in eclipse, but I'll still try and
> generate stackTrace
>

--bcaec53d588791e0a904c58722a7--