[
https://issues.apache.org/jira/browse/PHOENIX-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-3045:
-----------------------------------
Attachment: PHOENIX-3045_v1.patch
HTableInterfaces are not throwing TableNotFountException instead it saying like
this
{code}
2016-06-25 03:42:22,370 ERROR
[phoenix-longrunning-env-13.openstacklocal,16020,1466823559126-recovery-writer--pool5-t2]
client.AsyncProcess: Cannot get replica 0 location for
{"totalColumns":2,"row":"\\xC7\\x03\\x04\"L\\x06\\x00\\xC2\\x02\\x14\\x00\\xC2\\x02\\x1A\\x00\\x80\\x9A\\xE0\\x82","families":{"0":[{"qualifier":"_0","vlen":2,"tag":[],"timestamp":1466825784753},{"qualifier":"0:UNSIG_DATE_ID","vlen":8,"tag":[],"timestamp":1466825784753}]}}
{code}
As per you review comments, I have updated the patch by creating
RecoveyIndexWriter (derived class of IndexWriter).
> 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)
