phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maddineni Sukumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3928) Consider retrying once after any SQLException
Date Thu, 15 Jun 2017 00:52:00 GMT

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

Maddineni Sukumar commented on PHOENIX-3928:
--------------------------------------------

Yes [~jamestaylor],  Index delete didnt change source table timestamp, so when we try force
update it is getting same timestamp from client and server,
 so server is not sending latest table object when timestamps are same.  

One option is when we force update cache cleaning table other info like indexes/views info.

> 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