On Wed, Apr 20, 2011 at 10:12 AM, Peter Haidinyak <phaidin...@local.com> wrote: > Sorry, my bad, I assumed each thread would have its own Table instance not > using a shared instance.
Yeah you'd need to use one HTable instance per thread. <plug>Alternatively, you can look at asynchbase, an alternative HBase client that's fully asynchronous and non-blocking and written from the ground-up to be thread safe. It performs much better than HTable for high-throughput low-latency multi-threaded applications: github.com/stumbleupon/asynchbase </plug> -- Benoit "tsuna" Sigoure Software Engineer @ www.StumbleUpon.com
