Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-1734

Java client timeout exceptions aren't useful

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.0
    • Fix Version/s: 1.1.0
    • Component/s: client
    • Target Version/s:

      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.

        Attachments

          Activity

            People

            • Assignee:
              jdcryans Jean-Daniel Cryans
              Reporter:
              mjacobs Matthew Jacobs
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: