[
https://issues.apache.org/jira/browse/HBASE-18829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajeshbabu Chintaguntla updated HBASE-18829:
--------------------------------------------
Attachment: HBASE-18829.patch
Here is the patch with the test case simulates the issue at PHOENIX-3111. I
agree with [~sergey.soldatov] and [~vincentpoon] that even without this change
the functionality of retrying the query can be achieved by checking in the
coprocessors that whether splitting/closing happening or not. But with this the
HBase itself takes care of retrying when the region closing/splitting without
any special handling.
> 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-18829.patch
>
>
> 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)
