bq. "but in real it is one message write in whereas the other message dropped."
Have you tried to set logging at DEBUG level (hbase package on client side)? You'll get helpful messages to analyse what happened. Even if classes are not thread-safe I'm not sure it's common to miss some operations. On Sat, Jun 7, 2014 at 4:57 PM, Hotec04 <[email protected]> wrote: > Yes, I set the autoflush to false. At first I tried to use table.put to add > rows and at last do one flush. But in that situation, only one row is added > into HTable. Then I changed to flush every time putting a row. > > The message drop situation happens in this scenario: I have 4 threads > running, each of them created their own Htable object under > connection.getTable(). When two of thread tried to do a flush at the same > time, ideally one should go in and the other should wait, but in real it is > one message write in whereas the other message dropped. > > Thank you! > > > > -- > View this message in context: > http://apache-hbase.679495.n3.nabble.com/Discuss-HBase-with-multiple-threads-tp4060081p4060111.html > Sent from the HBase User mailing list archive at Nabble.com. > -- Adrien Mogenet http://www.borntosegfault.com
