[
https://issues.apache.org/jira/browse/HBASE-18829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168680#comment-16168680
]
Vincent Poon commented on HBASE-18829:
--------------------------------------
PHOENIX-3111 introduced a preClose() hook which stalls the region closing until
all scanners are done, which sidesteps the race condition in HBASE-14893.
However, that is problematic because it might stall forever - PHOENIX-4214
Assuming PHOENIX-4214 can be fixed, then HBASE-14893 doesn't matter to Phoenix.
The decision to revert / not-revert should be based on its correctness from
HBase's perspective.
> 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
> Assignee: Ted Yu
> Attachments: 18829.v1.txt
>
>
> 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)
