> I think I'll go initially with cached HBaseConfiguration and one new
> HTable instance per request thread and accept the resulting slowness
> overhead per request.
Note, you should do this in a ThreadLocal, so you only accept slowness
on the initial request handled by a specific thread. That is
s,
jp
-Original Message-
From: saint@gmail.com [mailto:saint@gmail.com] On Behalf Of
stack
Sent: Wednesday, September 16, 2009 11:23 AM
To: hbase-user@hadoop.apache.org
Subject: Re: HBase Client Concerns
On Wed, Sep 16, 2009 at 11:16 AM, Jeyendran Balakrishnan <
jbalakrish...@do
---
> From: saint@gmail.com [mailto:saint@gmail.com] On Behalf Of
> stack
> Sent: Wednesday, September 16, 2009 10:16 AM
> To: hbase-user@hadoop.apache.org
> Subject: Re: HBase Client Concerns
>
> HTable is not thread-safe (See javadoc class comment). Use an HTable
>
:saint@gmail.com] On Behalf Of
stack
Sent: Wednesday, September 16, 2009 10:16 AM
To: hbase-user@hadoop.apache.org
Subject: Re: HBase Client Concerns
HTable is not thread-safe (See javadoc class comment). Use an HTable
per
Thread or use HTablePool. Internally, it carries a write buffer to
which
access
of the app?
>
> Thanks,
> jp
>
>
> -Original Message-
> From: Barney Frank [mailto:barneyfran...@gmail.com]
> Sent: Tuesday, September 15, 2009 4:41 PM
> To: hbase-user@hadoop.apache.org
> Subject: Re: HBase Client Concerns
>
> My app will be "highly threade
ver, and using the reference to
that instantiated HTable for the duration of the app?
Thanks,
jp
-Original Message-
From: Barney Frank [mailto:barneyfran...@gmail.com]
Sent: Tuesday, September 15, 2009 4:41 PM
To: hbase-user@hadoop.apache.org
Subject: Re: HBase Client Concerns
My a
My app will be "highly threaded" some day. I was trying to avoid creating
another thread for Hbase and use the pool instead. About 33% of the
requests handled in the app server will need to retrieve data from Hbase. I
was hoping to leverage the HTablePool rather than managing my own pool or
crea
On Tue, Sep 15, 2009 at 3:13 PM, Barney Frank wrote:
> This is despite the fact that I set hbase.pause to be 25 ms and the
> retries.number = 2.
>
>
Yeah, this is down in guts of the hadoop rpc we use. Around connection
setup it has its own config. that is not well aligned with o
Hopefully I am doing something wrong and y'all can help me see it.
I am working on an application that utilizes Hbase for real-time queries.
The dependency on Hbase is not critical so if HBase is not available for any
reason the application should continue on doing its job without the data
from Hb
