[
https://issues.apache.org/jira/browse/HBASE-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596263#comment-13596263
]
nkeywal commented on HBASE-7989:
--------------------------------
Yes. There is a 20s timout for connect by default. And here there are two
issues:
- we should be able to have a much lower timeout for connect as it doesn't
depend on GC stuff and it's a clear error (we are sure that the action is not
done on the server, contrary to a read or write timeout)
- we should not even go to the server in some cases (we know it's dead).
> Client with a cache info on a dead server will wait for 20s before trying
> another one.
> --------------------------------------------------------------------------------------
>
> Key: HBASE-7989
> URL: https://issues.apache.org/jira/browse/HBASE-7989
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.95.0, 0.98.0
> Reporter: nkeywal
>
> Scenario is:
> - fetch the cache in the client
> - a server dies
> - try to use a region that is on the dead server
> This will lead to a 20 second connect timeout. We don't have this in unit
> test because we have this only is the remote box does not answer. In the unit
> tests we have immediately a connection refused from the OS.
--
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
