Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Tue, 19 Nov 2013 08:43:23 +0000 (UTC)
From: "Liang Xie (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12679901.1384850554520.97069.1384850603545@arcas>
In-Reply-To: <JIRA.12679901.1384850554520@arcas>
References: <JIRA.12679901.1384850554520@arcas>
Subject: [jira] [Created] (HBASE-9996) move the log io operation out of
 updateLock scope
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Liang Xie created HBASE-9996:
--------------------------------

             Summary: 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


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)