Re: hbase row locking

[abhishek1015 <ab...@gmail.com>]

I set the durability of both tables to SYNC_WAL and changed the network delay
using 'tc' command from .1ms to 20ms to 200ms. I  see throughput to be 1500,
58 and 6 per regionserver respectively for both schema. This was unexpected
as I was certainly hoping to see row locking for wide table case.

Thanks
Abhishek 



--
View this message in context: http://apache-hbase.679495.n3.nabble.com/hbase-row-locking-tp4064432p4064972.html
Sent from the HBase User mailing list archive at Nabble.com.

Re: hbase row locking

[abhishek1015 <ab...@gmail.com>]

Thanks lars for sharing HBASE-4528. I was not aware of this impl
optimization.
Abhishek



--
View this message in context: http://apache-hbase.679495.n3.nabble.com/hbase-row-locking-tp4064432p4064988.html
Sent from the HBase User mailing list archive at Nabble.com.

Re: hbase row locking

[lars hofhansl <la...@apache.org>]

What are you trying to prove/observe, Abhishek?
HBase does not hold the row lock while the WAL is sync'ed (see my previous response), so network settings would have no bearing on how long the row locks are being held.See HBASE-4528. You'd to go back to an 0.92 release to still observe that effect.

-- Lars

     From: abhishek1015 <ab...@gmail.com>
 To: user@hbase.apache.org 
 Sent: Saturday, October 11, 2014 9:39 PM
 Subject: Re: hbase row locking
   
I set the durability of both tables to SYNC_WAL and changed the network delay
using 'tc' command from .1ms to 20ms to 200ms. I  see throughput to be 1500,
58 and 6 per regionserver respectively for both schema. This was unexpected
as I was certainly hoping to see row locking for wide table case.

Thanks
Abhishek 



--
View this message in context: http://apache-hbase.679495.n3.nabble.com/hbase-row-locking-tp4064432p4064972.html


Sent from the HBase User mailing list archive at Nabble.com.