[
https://issues.apache.org/jira/browse/PHOENIX-5178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790568#comment-16790568
]
Josh Elser commented on PHOENIX-5178:
-------------------------------------
{quote}an exception handling of AccessDeniedException is covering this bug and
not affecting the user connection as it's timestamp is always greater than the
meta timestamp.
{quote}
Gotcha. Thanks for the explanation.
Good catch on your addendum too ;) I didn't think about rolling over :)
> SYSTEM schema is not getting cached at MetaData server
> ------------------------------------------------------
>
> Key: PHOENIX-5178
> URL: https://issues.apache.org/jira/browse/PHOENIX-5178
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.8.0
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
> Priority: Major
> Fix For: 4.15.0
>
> Attachments: PHOENIX-5178.patch, PHOENIX-5178_v1-addendum.patch,
> PHOENIX-5178_v1.patch
>
>
> During initialization, the meta connection will not be able to see the SYSTEM
> schema as the scanner at meta server is running with max_timestamp of
> MIN_SYSTEM_TABLE_TIMESTAMP(exclusive) which result in a new connection to
> create SYSTEM schema metadata everytime.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
