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

Hadoop QA commented on HBASE-17534:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s 
{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 0m 4s {color} 
| {color:red} Docker failed to build yetus/hbase:e01ee2f. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12865779/HBASE-17534.004.branch-1.patch
 |
| JIRA Issue | HBASE-17534 |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/6666/console |
| Powered by | Apache Yetus 0.3.0   http://yetus.apache.org |


This message was automatically generated.



> 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
>
>
> 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