[
https://issues.apache.org/jira/browse/PHOENIX-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896373#comment-16896373
]
Chinmay Kulkarni commented on PHOENIX-5403:
-------------------------------------------
[~tdsilva] what is the logic behind the
{code:java}
int maxTryCount = tenantId == null ? 1 : 2;
{code}
Why are we trying twice in case a tenantID is specified? Can you please add a
comment there? Otherwise lgtm. Thanks!
> Optimize metadata cache lookup of global tables using a tenant specific
> connection
> ----------------------------------------------------------------------------------
>
> Key: PHOENIX-5403
> URL: https://issues.apache.org/jira/browse/PHOENIX-5403
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.2
> Reporter: Thomas D'Silva
> Assignee: Chinmay Kulkarni
> Priority: Major
> Fix For: 4.15.0, 5.1.0
>
> Attachments: PHOENIX-5403-v2.patch, PHOENIX-5403-v3.patch,
> PHOENIX-5403-v4.patch, PHOENIX-5403.patch, diff.patch
>
>
> If we use a teanant specific connection to look up a global table we always
> make an rpc to the server even if the UPDATE_CACHE_FREQUENCY is set on the
> table.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
