Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Wed, 1 Apr 2015 15:13:53 +0000 (UTC)
From: "John Leach (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12787367.1427901178000.93322.1427901233004@Atlassian.JIRA>
In-Reply-To: <JIRA.12787367.1427901178000@Atlassian.JIRA>
References: <JIRA.12787367.1427901178000@Atlassian.JIRA>
 <JIRA.12787367.1427901178855@arcas>
Subject: [jira] [Created] (HBASE-13378) RegionScannerImpl synchronized for
 READ_UNCOMMITTED Isolation Levels
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

John Leach created HBASE-13378:
----------------------------------

             Summary: RegionScannerImpl synchronized for READ_UNCOMMITTED Isolation Levels
                 Key: HBASE-13378
                 URL: https://issues.apache.org/jira/browse/HBASE-13378
             Project: HBase
          Issue Type: New Feature
            Reporter: John Leach
            Priority: Minor


This block of code below coupled with the close method could be changed so that READ_UNCOMMITTED does not synchronize.  

{CODE:JAVA}
      // synchronize on scannerReadPoints so that nobody calculates
      // getSmallestReadPoint, before scannerReadPoints is updated.
      IsolationLevel isolationLevel = scan.getIsolationLevel();
      synchronized(scannerReadPoints) {
        this.readPt = getReadpoint(isolationLevel);
        scannerReadPoints.put(this, this.readPt);
      }
{CODE}

This hotspots for me under heavy get requests.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)