[ 
https://issues.apache.org/jira/browse/HBASE-17534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997109#comment-15997109
 ] 

Hudson commented on HBASE-17534:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.3-IT #38 (See 
[https://builds.apache.org/job/HBase-1.3-IT/38/])
HBASE-17534 Avoid re-wrapping IOExceptions as IOExceptions (elserj: rev 
2ddb30c570ce239c4fb81213d468452709b14d78)
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/SecureBulkLoadClient.java
* (add) 
hbase-client/src/test/java/org/apache/hadoop/hbase/client/coprocessor/TestSecureBulkLoadClient.java


> SecureBulkLoadClient squashes DoNotRetryIOExceptions from the server
> --------------------------------------------------------------------
>
>                 Key: HBASE-17534
>                 URL: https://issues.apache.org/jira/browse/HBASE-17534
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.4.0, 1.2.6, 1.3.2, 1.1.11
>
>         Attachments: HBASE-17534.001.branch-1.patch, 
> HBASE-17534.002.branch-1.patch, HBASE-17534.003.branch-1.patch, 
> HBASE-17534.004.branch-1.patch, HBASE-17534.005.branch-1.patch, 
> HBASE-17534.006.branch-1.patch
>
>
> While writing some tests against 1.x, I noticed that what should have been a 
> DoNotRetryIOException sent to the client from a RegionServer was getting 
> retried until it reached the hbase client retries limit.
> Upon inspection, I found that the SecureBulkLoadClient was wrapping all 
> Exceptions from the RPC as an IOException. I believe this is creating a case 
> where the RPC system doesn't notice that there's a DNRIOException wrapped 
> beneath it, thinking it's a transient error.
> This results in clients having to wait for the retry limit to be reached 
> before they get acknowledgement that something failed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to