[ https://issues.apache.org/jira/browse/HBASE-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-1213. -------------------------- Resolution: Duplicate Resolving as duplicate of the WAL batching work that has been done of late; this issue talks about batching going into WAL > [performance] Investigate Locking & Contention in the Write Path > ---------------------------------------------------------------- > > Key: HBASE-1213 > URL: https://issues.apache.org/jira/browse/HBASE-1213 > Project: HBase > Issue Type: Improvement > Components: performance > Affects Versions: 0.19.0 > Reporter: Ben Maurer > Assignee: stack > > 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. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira