You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Jeffrey Zhong (JIRA)" <ji...@apache.org> on 2014/04/08 03:35:14 UTC

[jira] [Updated] (PHOENIX-916) Time clock skew issue when SYSTEM.CATALOG moves between region servers

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

Jeffrey Zhong updated PHOENIX-916:
----------------------------------

    Attachment: phoenix-916.patch

Basically we delay the SYSTEM.CATALOG region open a little bit to compensate the possible time clock skew. If later we want more accurate sleep time in the future, we can do that by remembering the server time when region closing and current server time when opening.

> Time clock skew issue when SYSTEM.CATALOG moves between region servers
> ----------------------------------------------------------------------
>
>                 Key: PHOENIX-916
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-916
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 4.0.0, 5.0.0
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>            Priority: Critical
>         Attachments: phoenix-916.patch
>
>
> Since we rely on the sever time stamp of RS which is hosting SYSTEM.CATALOG. When the table moves to another region server, the server time may decrease(increasing is all right). This may cause a query doesn't return anything though it should be.



--
This message was sent by Atlassian JIRA
(v6.2#6252)