You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Vincent Poon (JIRA)" <ji...@apache.org> on 2019/04/01 17:35:00 UTC
[jira] [Commented] (PHOENIX-5193) Handle SQLException:ERROR 2008
(INT10) in PhoenixIndexFailurePolicy#doBatchWithRetries
[ https://issues.apache.org/jira/browse/PHOENIX-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807016#comment-16807016 ]
Vincent Poon commented on PHOENIX-5193:
---------------------------------------
[~mihir6692] I think we should call clearTableRegionCache() and setMetdataOnMutations() here if we get INDEX_METADATA_NOT_FOUND.
Otherwise, there's no point in retrying if the metadata still won't be there the next attempt.
And conversely, in PHOENIX-5194 we shouldn't be calling these methods for any IOException, which could be unrelated to index metadata.
> 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.15.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)