[KUDU-1734] Java client timeout exceptions aren't useful

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.1.0
• Component/s: client
• Labels: client impala usability
• Target Version/s: 1.1.0
• Assignee: Jean-Daniel Cryans
• Reporter: Matthew Jacobs
• Created: 25/Oct/16 22:59
• Updated: 31/Oct/16 16:33
• Resolved: 31/Oct/16 16:33

Description

When a timeout occurs in the Java client, it throws exceptions that are very verbose and hard to make use of.

For example:

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)

Most of the information isn't useful to the caller.