[
https://issues.apache.org/jira/browse/PHOENIX-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376559#comment-15376559
]
Ankit Singhal commented on PHOENIX-3045:
----------------------------------------
[~enis]
bq. Do we need to handle disabled index tables as well, or throwing it back is
the correct semantics?
Index tables are disabled only during the drop of the table so if client quits
abruptly after disable and before the delete of the table , then this case may
happen. Which I think is ok ,as client knew that some cleanup is not done and
he has to drop the index again or drop the index table from hbase shell.
> Data regions in transition forever if RS holding them down during drop index
> ----------------------------------------------------------------------------
>
> Key: PHOENIX-3045
> URL: https://issues.apache.org/jira/browse/PHOENIX-3045
> Project: Phoenix
> Issue Type: Bug
> Reporter: Sergio Peleato
> Assignee: Ankit Singhal
> Fix For: 4.8.0
>
> Attachments: PHOENIX-3045.patch, PHOENIX-3045_v1.patch,
> PHOENIX-3045_v2.patch
>
>
> There is a chance that region server holding the data regions might abruptly
> killed before flushing the data table this leads same failure case that data
> regions won't be opened which leads to the regions in transition forever. We
> need to handle this case by checking dropped indexes on recovery write
> failures and skip the corresponding mutations to write to them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
