[
https://issues.apache.org/jira/browse/KUDU-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-1878:
--------------------------------
Code Review: https://gerrit.cloudera.org/#/c/7146/
> Java openTable() call eagerly connects to all tablets
> -----------------------------------------------------
>
> Key: KUDU-1878
> URL: https://issues.apache.org/jira/browse/KUDU-1878
> Project: Kudu
> Issue Type: Bug
> Components: client, impala, java, perf
> Affects Versions: 1.2.0
> Reporter: Todd Lipcon
> Assignee: Alexey Serbin
> Priority: Critical
> Labels: ramp-up
>
> In a secure cluster, I noticed that every time I run an Impala query, it
> issues new service tickets for every tablet server on the coordinator node.
> It seems like it is creating a new connection to each tablet server, despite
> not actually needing to access any data. This is probably a big part of why
> planning is slow for larger clusters.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
