Thank you for the answer.
On Mon, Dec 15, 2008 at 5:48 PM, Slava Gorelik <[email protected]> wrote: > As far as i know the HTable itself has connection pool (HConnectionManager > is singleton).I think, multiple instances of HTable within same application > will not help you. > You better try to use multiple process instead of multiple threads. > > You can search the mailing list archive, i asked almost same question. > Current HBase client implementation has some RPC Lock, i.e. multi-threading > is not useful. > > Best Regards. > > On Mon, Dec 15, 2008 at 12:23 PM, Michael Dagaev > <[email protected]>wrote: > >> Hi, all >> >> Currently, we are using a single instance of HTable in a >> multithreaded application. That is, several threads use the same >> instance of HTable to insert data in the database. Since method >> "commit" of HTable is synchronized, we are afraid that the single >> instance of HTable can be a bottle neck. So, we are going to create a >> pool of HTable instances (all instances are created with the same >> table name) and use the instances simultaneously (an instance per >> thread). >> >> Does it make sense? >> >> Thank you for your cooperation, >> M. >> >
