[
https://issues.apache.org/jira/browse/PHOENIX-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793281#comment-16793281
]
Monani Mihir commented on PHOENIX-5193:
---------------------------------------
>> The comment there says "If it fails again, we don't retry". Wouldn't the
>> behavior here be different - we would retry multiple times?
This patch is about handling retries which will be done in
PhoenixIndexFailurePolicy#doBatchWithRetries.
This case is about first getting *INDEX_WRITE_FAILURE* and then while we do
Index retires, catching *NDEX_METADATA_NOT_FOUND*** in doBatchWithRetries().
>> Just saw that you're calling `clearTableRegionCache` in PHOENIX-5194
PHOENIX-5194 is another part of solution for PHOENIX-5092 , in the case where
we might be using old cached location of regions for index and data table while
we do index retries in doBatchWithRetries().
> Handle SQLException:ERROR 2008 (INT10) in
> PhoenixIndexFailurePolicy#doBatchWithRetries
> ---------------------------------------------------------------------------------------
>
> Key: PHOENIX-5193
> URL: https://issues.apache.org/jira/browse/PHOENIX-5193
> Project: Phoenix
> Issue Type: Sub-task
> Affects Versions: 4.14.0, 5.0.0, 4.14.1
> Reporter: Monani Mihir
> Assignee: Monani Mihir
> Priority: Critical
> Attachments: PHOENIX-5193-4.x-HBase-1.3.01.patch
>
>
> In MutationState#send(Iterator<TableRef>)#doMutation , we use htable.batch()
> which will throw SQLException wrapped in
> RetriesExhaustedWithDetailsException.
> These wrapped SQLException are of two types,
> 1) INDEX_WRITE_FAILURE(1121, "XCL21", "Write to the index failed.")
> 2) INDEX_METADATA_NOT_FOUND(2008, "INT10", "Unable to find cached index
> metadata. ")
> Out of this we only handle 1st (INDEX_WRITE_FAILURE) and we should handle 2nd
> one too (INDEX_METADATA_NOT_FOUND)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
