[
https://issues.apache.org/jira/browse/PHOENIX-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963620#comment-13963620
]
James Taylor commented on PHOENIX-916:
--------------------------------------
Please add your new config param ("phoenix.clock.skew.interval") as static
constant in org.apache.phoenix.query.QueryServices and add your default (2000)
as a static constant in org.apache.phoenix.query.QueryServicesOptions.
Also, please document in the table on this page as well:
http://phoenix.incubator.apache.org/tuning.html
One minor nit: I don't think the if (env == null) check is necessary.
> 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-v2.patch, 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)
