[
https://issues.apache.org/jira/browse/HBASE-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-1213:
-------------------------
Summary: [performance] Investigate Locking & Contention in the Write Path
(was: Investigate Locking & Contention in the Write Path)
Added performance label to subject.
Would do this optimization only when the batch of edits was above some
threshold -- say at least a batch of ten edits.
> [performance] Investigate Locking & Contention in the Write Path
> ----------------------------------------------------------------
>
> Key: HBASE-1213
> URL: https://issues.apache.org/jira/browse/HBASE-1213
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.19.0
> Reporter: Ben Maurer
> Assignee: stack
> Fix For: 0.20.0
>
>
> When doing a large number of bulk updates from different clients, I noticed
> that there was a high level of lock contention for stuff like locking the
> HLog. It seems that each thread acquires the lock for a single BatchUpdate,
> releases the lock then another thread owns the lock before the initial writer
> gets to the next update. Having the threads bounce around may lead to
> suboptimal performance.
> Should be benchmarked & maybe changed to have less context switching.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
