hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1920) Client with cached region location pointing at dead server does not recover
Date Tue, 03 Nov 2009 21:13:32 GMT

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

stack commented on HBASE-1920:
------------------------------

@jgray, does this require there to be one RS only?

> Client with cached region location pointing at dead server does not recover
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-1920
>                 URL: https://issues.apache.org/jira/browse/HBASE-1920
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.1
>            Reporter: Jonathan Gray
>            Priority: Critical
>             Fix For: 0.20.2, 0.21.0
>
>
> Testing in HBASE-1908 uncovered an issue where I had a client that had cached a region
location.  I killed that regionserver, waited for recovery/reassignment, and then tried to
scan the table again from the same client w/o restarting it.
> A client normally gets a NotServingRegionException when a region is reassigned, but since
this server is dead the client just got Connection Refused type exceptions.  These didn't
seem to trigger the client to ask META for a new region location.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message