[
https://issues.apache.org/jira/browse/HBASE-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747272#comment-13747272
]
Nicolas Liochon commented on HBASE-9268:
----------------------------------------
bq. How do you define "new" here? I haven't tested it but I'm pretty sure this
wasn't an issue in 0.94.
Yeah, that's the 0.94 I was thinking about. The code has changed a lot around
this area, but in HBaseClient.java it seems like in 0.95: no timeouts on
writes. So I wonder what's the extra logic that makes it work on 0.94 (it's not
purely theoretical: we could have this issue somewhere else in 0.95). I'm going
to try the 0.94 to be sure.
bq. It worked fine with HBASE-7590 once I fixed the class name in the release
note
Thanks for the test and the fix, JD.
> Client doesn't recover from a stalled region server
> ---------------------------------------------------
>
> Key: HBASE-9268
> URL: https://issues.apache.org/jira/browse/HBASE-9268
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.95.2
> Reporter: Jean-Daniel Cryans
> Assignee: Nicolas Liochon
> Fix For: 0.98.0, 0.95.3
>
> Attachments: 9268-hack.patch
>
>
> Got this testing the 0.95.2 RC.
> I killed -STOP a region server and let it stay like that while running PE.
> The clients didn't find the new region locations and in the jstack were stuck
> doing RPC. Eventually I killed -CONT and the client printed these:
> bq. Exception in thread "TestClient-6" java.lang.RuntimeException:
> org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed
> 128 actions: IOException: 90 times, SocketTimeoutException: 38 times,
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
