You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/01/24 03:56:39 UTC
[jira] [Resolved] (PHOENIX-1688) dropSequence uses
HConstants.LATEST_TIMESTAMP as the Append timestamp
[ https://issues.apache.org/jira/browse/PHOENIX-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor resolved PHOENIX-1688.
-----------------------------------
Resolution: Not A Problem
Looks like a test-only issue.
> 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
>
> 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)