[
https://issues.apache.org/jira/browse/HBASE-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990472#comment-12990472
]
ryan rawson commented on HBASE-3504:
------------------------------------
But doesn't each appending thread need to atomically do some work? A read
write lock would not maintain that atomic semantics?
https://issues.apache.org/jira/browse/HBASE-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990470#comment-12990470]
the lock in Write mode while the HLog.append() calls could acquire it in
Read mode.
logSyncer thread invokes HDFS.sync on a writer that has already been closed
by the log-roller.This could happen because the logSyncer thread does not
acquire the updateLock while invoking HDFS sync on the writer.
to the HDFS log file. This is a scalability bottleneck for a workload that
comprises mostly of counter-increments.
> HLog performance improvement
> ----------------------------
>
> Key: HBASE-3504
> URL: https://issues.apache.org/jira/browse/HBASE-3504
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
>
> The HLog.updateLock protects the rolling of logs with concurrent writes to
> the HDFS log file. This is a scalability bottleneck for a workload that
> comprises mostly of counter-increments.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
