[ https://issues.apache.org/jira/browse/KUDU-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Serbin updated KUDU-1878: -------------------------------- Resolution: Fixed Fix Version/s: 1.5.0 Status: Resolved (was: In Review) Fixed with 58248841f213a64683ee217f025f0a38a8450f74 > 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 > Fix For: 1.5.0 > > > 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)