Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 9 Jul 2016 04:39:11 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12986059.1467350400000.65103.1468039151089@Atlassian.JIRA>
In-Reply-To: <JIRA.12986059.1467350400000@Atlassian.JIRA>
References: <JIRA.12986059.1467350400000@Atlassian.JIRA> <JIRA.12986059.1467350400816@arcas>
Subject: [jira] [Commented] (HBASE-16161) Remove a few unnecessary
 (uncontended) synchronizes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 09 Jul 2016 04:39:13 -0000


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

stack commented on HBASE-16161:
-------------------------------

Over in review @heng chen suggestion that I add a test to prove concurrency on next in RegionScanner is good absent synchronize seems good to me. Let me do it.

> Remove a few unnecessary (uncontended) synchronizes
> ---------------------------------------------------
>
>                 Key: HBASE-16161
>                 URL: https://issues.apache.org/jira/browse/HBASE-16161
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>            Priority: Minor
>         Attachments: HBASE-16161.branch-1.001.patch
>
>
> This is followon from HBASE-15716. We have a few odd looking synchronizes.  A few are probably elided after analysis concludes single thread consumer but lets remove to be clear.


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