phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3928) Consider retrying once after any SQLException
Date Fri, 16 Jun 2017 07:05:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16051498#comment-16051498
] 

James Taylor commented on PHOENIX-3928:
---------------------------------------

Sounds like it might be a bug. Does the server send over the updated table and then it's ignored
because the time stamp didn't change? Perhaps we can remove the cached table and add the new
one if the server sent it over (as opposed to the case where it sends null back)?

> Consider retrying once after any SQLException
> ---------------------------------------------
>
>                 Key: PHOENIX-3928
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3928
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Maddineni Sukumar
>             Fix For: 4.12.0
>
>
> There are more cases in which a retry would successfully execute than when a MetaDataEntityNotFoundException.
For example, certain error cases that depend on the state of the metadata would work on retry
if the metadata had changed. We may want to retry on any SQLException and simply loop through
the tables involved (plan.getSourceRefs().iterator()), and if any meta data was updated, go
ahead and retry once.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message