[
https://issues.apache.org/jira/browse/KUDU-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995540#comment-16995540
]
Zoltán Borók-Nagy commented on KUDU-3019:
-----------------------------------------
Thanks for looking at it, [~tlipcon].
It's version 1.6.0. The timeouts are the Impala defaults, which means 180000ms
for "defaultAdminOperationTimeoutMs" and "defaultOperationTimeoutMs" for the
Kudu client. The query hangs for hours in that RPC call.
I'm seeing it at a customer, not able to repro.
> Kudu client hangs in Deffered.join()
> ------------------------------------
>
> Key: KUDU-3019
> URL: https://issues.apache.org/jira/browse/KUDU-3019
> Project: Kudu
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Zoltán Borók-Nagy
> Priority: Major
>
> In Impala we've seen the Kudu client hanging with the following stack trace:
> {noformat}
> Thread 53015: (state = BLOCKED)
> - java.lang.Object.wait(long) @bci=0 (Compiled frame; information may be
> imprecise)
> - java.lang.Object.wait() @bci=2, line=502 (Compiled frame)
> - com.stumbleupon.async.Deferred.doJoin(boolean, long) @bci=77, line=1122
> (Compiled frame)
> - com.stumbleupon.async.Deferred.join() @bci=3, line=1006 (Compiled frame)
> -
> org.apache.kudu.client.KuduClient.joinAndHandleException(com.stumbleupon.async.Deferred)
> @bci=1, line=340 (Compiled frame)
> - org.apache.kudu.client.KuduClient.openTable(java.lang.String) @bci=10,
> line=212 (Compiled frame)
> -
> org.apache.impala.planner.KuduScanNode.init(org.apache.impala.analysis.Analyzer)
> @bci=32, line=115 (Compiled frame)
> -
> org.apache.impala.planner.SingleNodePlanner.createScanNode(org.apache.impala.analysis.TableRef,
> org.apache.impala.analysis.AggregateInfo,
> org.apache.impala.analysis.Analyzer) @bci=252, line=1312 (Compiled frame)
> ...{noformat}
> The client hangs in Deferred.join():
> [https://github.com/apache/kudu/blob/a8c6ea258c06407c1a4fef260da3a1cb70529bd9/java/kudu-client/src/main/java/org/apache/kudu/client/KuduClient.java#L423]
> To at least mitigate the problem, maybe Deferred.join(long timeout) could be
> used instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
