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 2015/02/27 01:31:04 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14339462#comment-14339462 ] 

James Taylor commented on PHOENIX-1688:
---------------------------------------

That code as removed to fix PHOENIX-1257 (which I asked specifically for you to review and you did). The same +1 is done, but in a different way - please review the commit for that fix. We may need to do something different specifically for sequences.

> 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)