[
https://issues.apache.org/jira/browse/HBASE-8776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691044#comment-13691044
]
stack commented on HBASE-8776:
------------------------------
40minutes is crazy. Can we change that? 10minutes is bad too. We are just
going to piss people off w/ timeouts like this.
I'd say default should ride over a RS crash (Interesting that in hbase-it, the
kills are clean).
40s was the timeout on zk but now it is whatever maxSessionTimeout is (180s in
0.94 and 90s in 0.95).
Where is our recovery from crashed regionserver in one minute! I thought I saw
a talk on that recently (smile). So we have to timeout zk -- 90s in trunk --
then do recovery a minute or so hopefully -- and then assign (tens of seconds)
for a total of 5minutes max (default should be sluggish in favor of things
continuing to chug along I'd say).
> port HBASE-8723 to 0.94
> -----------------------
>
> Key: HBASE-8776
> URL: https://issues.apache.org/jira/browse/HBASE-8776
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.8
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Fix For: 0.94.9
>
> Attachments: HBASE-8776-v0.patch
>
>
--
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
