HBase uses MVCC to deal with concurrent writes, this is a good explanation:
https://blogs.apache.org/hbase/entry/apache_hbase_internals_locking_and -- Iain Wright This email message is confidential, intended only for the recipient(s) named above and may contain information that is privileged, exempt from disclosure under applicable law. If you are not the intended recipient, do not disclose or disseminate the message to anyone except the intended recipient. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender by return email, and delete all copies of this message. On Tue, Aug 23, 2016 at 9:59 AM, Manjeet Singh <[email protected]> wrote: > Hi All, > In Hbase current version what happen if two different client write the same > rowkey at same time in hbase > Assume if its kind of update. > Does Rowkey lock Hbase server automatically deal with this? > > > Thanks > Manjeet > > On Wed, Aug 17, 2016 at 1:04 PM, Dima Spivak <[email protected]> wrote: > > > Row locks on the client side were deprecated in 0.94 (see HBASE-7341) and > > removed in 0.96 (see HBASE-7315). As you note, they could lead to > deadlocks > > and also had problems when region moves or splits occurred. > > > > Is there a specific reason you're looking for this functionality, > Manjeet? > > > > -Dima > > > > On Tuesday, August 16, 2016, Manjeet Singh <[email protected]> > > wrote: > > > > > Hi All > > > > > > Can anyone help me about how and in which version of Hbase support > Rowkey > > > lock ? > > > I have seen article about rowkey lock but it was about .94 version it > > said > > > that if row key not exist and any update request come and that rowkey > not > > > exist then in this case Hbase hold the lock for 60 sec. > > > > > > currently I am using Hbase 1.2.2 version > > > > > > Thanks > > > Manjeet > > > > > > > > > > > > -- > > > luv all > > > > > > > > > -- > > -Dima > > > > > > -- > luv all >
