hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13366) Throw DoNotRetryIOException instead of read only IOException
Date Tue, 31 Mar 2015 17:30:53 GMT

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

Nick Dimiduk commented on HBASE-13366:
--------------------------------------

What Elliott said. For that matter, we'd want some higher granularity -- is it all requests
that should not be retried? Seems in this case it should only be write requests. IIRC, DoNotRetry
exceptions have consequences to the client at layers beyond the individual request (i.e.,
location caching and the like).

> Throw DoNotRetryIOException instead of read only IOException
> ------------------------------------------------------------
>
>                 Key: HBASE-13366
>                 URL: https://issues.apache.org/jira/browse/HBASE-13366
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Liu Shaohui
>            Assignee: Liu Shaohui
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE-13366-v1.diff
>
>
> Currently, the read only region just throws an IOException to the clients who send write
requests to it. This will cause the clients retry for configured times or until operation
timeout.
> Changing this exception to DoNotRetryIOException will make the client failed fast.
> Suggestions are welcomed~ Thanks



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

Mime
View raw message