[jira] [Commented] (HBASE-18829) Consider reverting HBASE-14893 Race between mutation on region and region closing operation

["Lars Hofhansl (JIRA)" <ji...@apache.org>]

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

Lars Hofhansl commented on HBASE-18829:
---------------------------------------

My comment from HBASE-14893:

+1 on reverting.

The intention here was good.
At the same time I think that accommodating this way in HBase for an issue in Phoenix is too dangerous.


> Consider reverting HBASE-14893 Race between mutation on region and region closing operation
> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-18829
>                 URL: https://issues.apache.org/jira/browse/HBASE-18829
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>
> HBASE-14893 was brought to attention by [~rajeshbabu] over PHOENIX-3111.
> This issue is to consider reverting the fix from HBASE-14893 based on the following observations:
> * The closing boolean was intended to be acquired before taking the lock ([~enis])
> * Phoenix local index has evolved over the years, the situation leading to NotServingRegionException may not exist from Phoenix side
> * Even if the situation still exists, downstream project (Phoenix) should properly handle NotServingRegionException without change in locking scheme in hbase



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)