[
https://issues.apache.org/jira/browse/HBASE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773189#action_12773189
]
Jean-Daniel Cryans commented on HBASE-1920:
-------------------------------------------
Well it seems I'm not able anymore... Since I use java 7 on that cluster my
master crashed and was just unable to reassign so I was getting retries because
.META. was never updated. Now I retried scanning, killing (sometimes waiting,
sometimes not for reassignment), then scanning again at least 10 times and it's
always working just fine.
> 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.
