[
https://issues.apache.org/jira/browse/PHOENIX-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340578#comment-14340578
]
James Taylor commented on PHOENIX-1688:
---------------------------------------
I think we may need to understand the root cause a bit more by having a
specific scenario in which this fails, but I'm all for consistency. I'd think
we'd want to use LATEST_TIMESTAMP everywhere to find the sequence (in the
absence of a CURRENT_SCN attribute on the connection). There is no single
system.sequence RS, as the table is salted, so the RS that hosts a particular
sequence should be the one that gives back the timestamp.
> dropSequence uses HConstants.LATEST_TIMESTAMP as the Append timestamp
> ---------------------------------------------------------------------
>
> Key: PHOENIX-1688
> URL: https://issues.apache.org/jira/browse/PHOENIX-1688
> Project: Phoenix
> Issue Type: Bug
> Reporter: Jeffrey Zhong
> Assignee: Jeffrey Zhong
> Attachments: PHOENIX-1688.patch
>
>
> system.sequence isn't running on the same region server of system.catalog.
> When the Append uses HContants.LATEST_TIMESTAMP, the append will use the
> current server time of the RS which is hosting system.sequence table.
> If the two servers have time clock skew, then unexpected errors like
> SequenceNotFoundException will happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
