[
https://issues.apache.org/jira/browse/PHOENIX-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373143#comment-15373143
]
Jesse Yates commented on PHOENIX-3045:
--------------------------------------
FWIW, i don't remember the thoughts on using the caching factory. I can imagine
trying to save as much time and resources as possible, but since truly new
htables need to relookup region locations and possibly aren't using the same
threadpool (if the latter, could be a huge issue). However, in the scheme of
things, probably better to go with the CP factory instead, unless someone has a
compelling reason... and then documents that in the code :)
> 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, PHOENIX-3045_v1.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)
