[
https://issues.apache.org/jira/browse/HBASE-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751208#action_12751208
]
stack commented on HBASE-1815:
------------------------------
Working w/ JSharp, looking in the thread dumps, it looks like each thread has
to do ten retries sleeping a second between each retry. When many threads, we
get a lot of messages in the log about the failure to connect. Need to
recognize dead-remote-side and handle it promptly.
> HBaseClient can get stuck in an infinite loop while attempting to contact a
> failed regionserver
> -----------------------------------------------------------------------------------------------
>
> Key: HBASE-1815
> URL: https://issues.apache.org/jira/browse/HBASE-1815
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.20.0
> Environment: Ubuntu Linux (Linux <elided> 2.6.24-23-generic #1 SMP
> Wed Apr 1 21:43:24 UTC 2009 x86_64 GNU/Linux), java version "1.6.0_06",
> Java(TM) SE Runtime Environment (build 1.6.0_06-b02), Java HotSpot(TM) 64-Bit
> Server VM (build 10.0-b22, mixed mode)
> Reporter: Justin Lynn
> Fix For: 0.20.1
>
> Attachments: thrift_server_log_excerpt, thrift_server_threaddump,
> thrift_server_threaddump_1
>
>
> While using HBase Thrift server, if a regionserver goes down due to shutdown
> or failure clients will timeout because the thrift server cannot contact the
> dead regionserver.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
