[
https://issues.apache.org/jira/browse/KUDU-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606731#comment-15606731
]
Jean-Daniel Cryans commented on KUDU-1734:
------------------------------------------
Working on it :) https://gerrit.cloudera.org/#/c/4781/
> Java client timeout exceptions aren't useful
> --------------------------------------------
>
> Key: KUDU-1734
> URL: https://issues.apache.org/jira/browse/KUDU-1734
> Project: Kudu
> Issue Type: Improvement
> Components: client
> Affects Versions: 1.0.0
> Reporter: Matthew Jacobs
> Labels: client, impala, usability
>
> When a timeout occurs in the Java client, it throws exceptions that are very
> verbose and hard to make use of.
> For example:
> {code}
> CAUSED BY: NonRecoverableException: Timed out after 1ms when joining
> Deferred@1214130230(state=PENDING, result=null, callback=get tablet locations
> from the master for table Kudu Master -> release master lookup permit ->
> retry RPC -> org.apache.kudu.client.AsyncKuduClient$4@1da21658 -> wakeup
> thread Thread-7, errback=passthrough -> release master lookup permit -> retry
> RPC after error -> passthrough -> wakeup thread Thread-7)
> CAUSED BY: TimeoutException: Timed out after 1ms when joining
> Deferred@1214130230(state=PENDING, result=null, callback=get tablet locations
> from the master for table Kudu Master -> release master lookup permit ->
> retry RPC -> org.apache.kudu.client.AsyncKuduClient$4@1da21658 -> wakeup
> thread Thread-7, errback=passthrough -> release master lookup permit -> retry
> RPC after error -> passthrough -> wakeup thread Thread-7)
> {code}
> Most of the information isn't useful to the caller.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
