I also ran into similar problem with one of my secondary index implementation. But, i could not dig into the problem as i have to shift focus on some other stuff. I am also interested in knowing the resolution of this kind of problem in Coprocessors.
On Sat, Jan 12, 2013 at 5:38 PM, Ted <[email protected]> wrote: > Please take a look at hbase-6651 which improves thread safety of table > pool. > > Are you using hbase 0.94 ? > > Thanks > > On Jan 12, 2013, at 4:06 PM, Adrien Mogenet <[email protected]> > wrote: > > > Hi there, > > > > I'm experiencing some issues with CP. I'm trying to implement an indexing > > solution (inspired by Annop's slides). In pre-put, I trigger another > Put() > > in an external table (to build the secondary index). It works perfect for > > one client, but when I'm inserting data from 2 separate clients, I met > > issues with HTable object (the one used in pre-Put()), because it's not > > thread-safe. I decided to move on TablePool and that fixed my issue. > > > > But if I increase the write-load (and concurrency) HBase is throwing a > OOM > > exception because it can't create new native threads. Looking at HBase > > metrics "threads count", I see that roughly 3500 threads are created. > > > > I'm looking for documentation about how CPs are working with threads : > > what/when should I protect against concurrency issues ? How may I solve > my > > issue ? > > > > Help is welcome :-) > > > > -- > > Adrien Mogenet > > 06.59.16.64.22 > > http://www.mogenet.me > -- Thanks & Regards, Anil Gupta
