[
https://issues.apache.org/jira/browse/PHOENIX-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796384#comment-16796384
]
Abhishek Singh Chouhan commented on PHOENIX-5194:
-------------------------------------------------
> If during this retires Index region and Data table region moves , Index/Data
>table region location cache does not get updated
So we get NotServingRegionException by hitting the wrong region server? If
that's the case then the RegionMovedException/NSRE should itself be sufficient
for hbase client to clear the cache out.
> Thread Cache is not update for Index retries in for
> MutationState#send()#doMutation()
> -------------------------------------------------------------------------------------
>
> Key: PHOENIX-5194
> URL: https://issues.apache.org/jira/browse/PHOENIX-5194
> Project: Phoenix
> Issue Type: Sub-task
> Affects Versions: 4.14.0, 5.0.0, 4.15.0, 4.14.1
> Reporter: Monani Mihir
> Assignee: Monani Mihir
> Priority: Major
> Labels: client
> Attachments: PHOENIX-5194-4.x-HBase-1.3.01.patch,
> PHOENIX-5194-4.x-HBase-1.3.02.patch
>
>
> Wwhen Client is writing and Index Failures happens, MutationState#send() will
> use PhoenixIndexFailurePolicy#doBatchWithRetries to apply index mutations. If
> during this retires Index region and Data table region moves , Index/Data
> table region location cache does not get updated. Because of this client is
> keep trying to write in same location and get failures. After all retries are
> finished, it will simply disable Index and aborts the client thread.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
