hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "JH Lin" <match20...@163.com>
Subject Re:why use at least one rowlock to update
Date Mon, 28 Aug 2017 14:06:57 GMT

在2017年08月28 17时55分, "JH Lin"<match2008s@163.com>写道:

hi all,i dived into hbase source these days.when i read at the HRegion#doMiniBatchMutation(...)
block then one question flashed in my mind:why did writer use at least one rowlock to implement
mutation?(ie.Puts or Deletes etc)
 since  if i have 10 rows to update,then it means that 9 rows have no rowlocks.so is 'at least
one rowlock' more symbolic than practical significane?
 AFAIK now,i think it's used to verify hbase' basic functions eg. rowlock mechanism.
pardon me if it's a bit old,but i just wonder to know its principle inside it.
one more thing, my english is poor,so sorry for any typo.
many thanks~

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message