[
https://issues.apache.org/jira/browse/KUDU-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin resolved KUDU-3526.
---------------------------------
Fix Version/s: 1.18.0
1.17.1
Resolution: Fixed
> [java] Scanner should bound with a tserver in java client.
> ----------------------------------------------------------
>
> Key: KUDU-3526
> URL: https://issues.apache.org/jira/browse/KUDU-3526
> Project: Kudu
> Issue Type: Bug
> Reporter: Song Jiacheng
> Priority: Major
> Fix For: 1.18.0, 1.17.1
>
>
> We always meet the "scanner not found" exception while using presto + kudu,
> even if we have set the timeout of scanner very large.
> It turns out the scanner does not bound with the tserver which it first
> communicates with.
> Here is the code in scanNextRows of java client:
> {code:java}
> final ServerInfo info =
> tablet.getReplicaSelectedServerInfo(nextRequest.getReplicaSelection(),
> location); {code}
> It still trying to find the tserver by the locations and selection policy. So
> if the leader is changed and the next scan request is sent to the new leader,
> the tserver will response with the "scanner not found" exception.
> We should make the scanner bound with the tserver, like how it does in c++
> client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
