[
https://issues.apache.org/jira/browse/PHOENIX-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371041#comment-15371041
]
Rajeshbabu Chintaguntla commented on PHOENIX-3045:
--------------------------------------------------
As for the patch we are checking table exists or not for each wal edit having
index updates. This makes the recovery slower in normal cases as well right?
Can't we collect non existing tables on failures and keep the list until we
open region so that we need not check for every update. We can have the list in
Indexer and clear in postOpen.
> 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.9.0
>
> Attachments: PHOENIX-3045.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)
