[
https://issues.apache.org/jira/browse/PHOENIX-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793191#comment-16793191
]
Vincent Poon commented on PHOENIX-5193:
---------------------------------------
[~mihir6692] The comment there says "If it fails again, we don't retry".
Wouldn't the behavior here be different - we would retry multiple times?
Also, they call `connection.getQueryServices().clearTableRegionCache` there, we
should probably keep that same behavior
> 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)
