hbase-issues mailing list archives

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

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

Enis Soztutar commented on HBASE-13366:
---------------------------------------

Each replica of a region has a different encoded name, and each request (whether read or write)
comes with target encoded region name. In no case, a request intended for the primary ends
up routed to the secondary (even if they are in the same server). The client meta routing
/ caching layer also treats them as different regions in terms of routing. 

> 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