You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Amitanand Aiyer (JIRA)" <ji...@apache.org> on 2013/03/24 06:35:15 UTC

[jira] [Resolved] (HBASE-6813) Optimise the time spent holding the updateLock under log roll

     [ https://issues.apache.org/jira/browse/HBASE-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amitanand Aiyer resolved HBASE-6813.
------------------------------------

    Resolution: Fixed
      Assignee: Amitanand Aiyer
    
> 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
>            Assignee: Amitanand Aiyer
>            Priority: Minor
>             Fix For: 0.89-fb
>
>
> 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