[
https://issues.apache.org/jira/browse/PHOENIX-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962610#comment-13962610
]
James Taylor commented on PHOENIX-916:
--------------------------------------
We have MetaDataRegionObserver which may be a better home for this, as I
believe you could get rid of instanceof check and the table name check (as this
coprocessor is only installed on the meta data table).
Otherwise, looks good and handles this corner case nicely.
> 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)
