phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeffrey Zhong (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-1688) dropSequence uses HConstants.LATEST_TIMESTAMP as the Append timestamp
Date Fri, 27 Feb 2015 00:14:05 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeffrey Zhong updated PHOENIX-1688:
-----------------------------------
    Attachment: PHOENIX-1688.patch

[~giacomotaylor] I found that the partial fix(as following) from Phoenix-909 has been gone
for no reason:

{code}
              // Add one to server time since max of time range is exclusive
              // and we need to account of OSs with lower resolution clocks.
              if(scn < HConstants.LATEST_TIMESTAMP) {
                  scn++;
              }
{code}

The attached patch adds that back as well.

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

Mime
View raw message