[jira] [Resolved] (KUDU-1468) Java client scan failures are not easy to diagnose root cause

["Jean-Daniel Cryans (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans resolved KUDU-1468.
--------------------------------------
       Resolution: Duplicate
         Assignee: Jean-Daniel Cryans
    Fix Version/s: NA

Sounds good Todd.

> Java client scan failures are not easy to diagnose root cause
> -------------------------------------------------------------
>
>                 Key: KUDU-1468
>                 URL: https://issues.apache.org/jira/browse/KUDU-1468
>             Project: Kudu
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.9.0
>            Reporter: Todd Lipcon
>            Assignee: Jean-Daniel Cryans
>             Fix For: NA
>
>
> I currently have a table where a couple of tablets are in a bad state (no leader). When I try to scan, I get:
> Unexpected exception org.kududb.client.NonRecoverableException: Too many attempts: ScanRequest(scannerId=null, attempt=101)
> org.kududb.client.NonRecoverableException: Too many attempts: ScanRequest(scannerId=null, attempt=101)
> This error isn't very useful - it should have some kind of message about which tablet ID had the issue, and what the issue was.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)