hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9996) move the log io operation out of updateLock scope
Date Fri, 22 Nov 2013 07:45:08 GMT

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

stack commented on HBASE-9996:
------------------------------

Trunk does this already.

> move the log io operation out of updateLock scope
> -------------------------------------------------
>
>                 Key: HBASE-9996
>                 URL: https://issues.apache.org/jira/browse/HBASE-9996
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 0.94.13
>            Reporter: Liang Xie
>            Assignee: Liang Xie
>         Attachments: HBase-9996-0.94.txt
>
>
> I am working at another write outlier issue, and just saw this code pattern:
> {code}
> synchronized(updateLock) {
> ...
> LOG.info(xxx)
> ...
> }
> {code}
> let's move the log statement out of this sync block.  seems it's ok in trunk code, just
a 0.94 issue



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message