Dear Iars, Thanks so much for your reply!
In my case, I need to overwrite or update a HTable. If reading during the process of updating or overwriting, any exceptions will be thrown by HBase? If multiple instances for a HTable are used by multiple threads, there must be inconsistency among them, right? I guess caching must be done in HBase. So retrieving in HTable must be almost as fast as in memory? Best regards, Bing On Fri, Apr 13, 2012 at 6:17 AM, lars hofhansl <lhofha...@yahoo.com> wrote: > Hi Bing, > > Which part? The server certainly is thread safe. > The client is not, at least not all the way through. > > The main consideration is HTable, which is not thread safe, you need to > create one instance for each thread > (HBASE-4805 makes that much cheaper), store the HTable in a ThreadLocal > after creation, or use HTablePool. > > Please let me know if that answers your question. > > Thanks. > > -- Lars > > > ----- Original Message ----- > From: Bing Li <lbl...@gmail.com> > To: hbase-u...@hadoop.apache.org; user <user@hbase.apache.org> > Cc: > Sent: Thursday, April 12, 2012 3:10 PM > Subject: Is HBase Thread-Safety? > > Dear all, > > Is HBase thread-safety? Do I need to consider the consistency issue when > manipulating HBase? > > Thanks so much! > > Best regards, > Bing > >
