You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/11/06 23:12:32 UTC

[jira] Updated: (HBASE-1920) Client with cached region location pointing at dead server does not recover

     [ https://issues.apache.org/jira/browse/HBASE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-1920:
-------------------------

    Fix Version/s:     (was: 0.20.2)

Moving out of 0.20.2 after chatting w/ JGray.

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