hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6813) Optimise the time spent holding the updateLock under log roll
Date Wed, 19 Sep 2012 03:48:08 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458390#comment-13458390

Jean-Daniel Cryans commented on HBASE-6813:

We actually create the file outside of that lock, so it's cleanupCurrentWriter that needs
to be broken up.
> Optimise the time spent holding the updateLock under log roll
> -------------------------------------------------------------
>                 Key: HBASE-6813
>                 URL: https://issues.apache.org/jira/browse/HBASE-6813
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Amitanand Aiyer
>            Priority: Minor
> Log roll entails syncing the old log, closing it and creating a new log file.
> We currently do all the 3 steps while holding the updateLock. This causes latency spikes
for puts during this time.
> We only need to sync the old log under the lock. Creating the new file, can be done before
grabbing the lock. Closing the old file can be done after we release the lock.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message