[ https://issues.apache.org/jira/browse/HBASE-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504937#comment-13504937 ]
nkeywal commented on HBASE-5843: -------------------------------- Some more tests: ther scenario: 2 RS. Create a table with 3000 regions. Start a third RS. Kill -15 the second one: there are 1500 regions to reassign. I've made multiple measures, there are all there: It's in seconds. 0.96 trunk is patched with HBASE-7220 (no metrics at all). Creating a table with 3000 regions: 0.92: 261s; 260s 0.94.0: 260s; 260s 0.94.1: 261s; 260s 0.94 trunk: 292s; 281s; 282s; 0.96 trunk: 173s; 178s Reassign after the kill 0.92: 107s, 110s 0.94.0: 105s; 105s 0.94.1: 107s; 107s 0.94 trunk: 122s; 105s; 116s 0.96 trunk: 50s; 50s; Same test, but putting ZK on a separate node, 1Gb network. Reassign after the kill: 0.96 trunk: 101s. I need to do more tests, but it seems to match the profiling I've done; the time is now spent in ZK communications. > Improve HBase MTTR - Mean Time To Recover > ----------------------------------------- > > Key: HBASE-5843 > URL: https://issues.apache.org/jira/browse/HBASE-5843 > Project: HBase > Issue Type: Umbrella > Affects Versions: 0.96.0 > Reporter: nkeywal > Assignee: nkeywal > > A part of the approach is described here: > https://docs.google.com/document/d/1z03xRoZrIJmg7jsWuyKYl6zNournF_7ZHzdi0qz_B4c/edit > The ideal target is: > - failure impact client applications only by an added delay to execute a > query, whatever the failure. > - this delay is always inferior to 1 second. > We're not going to achieve that immediately... > Priority will be given to the most frequent issues. > Short term: > - software crash > - standard administrative tasks as stop/start of a cluster. -- 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