[
https://issues.apache.org/jira/browse/HBASE-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tianying Chang updated HBASE-5843:
----------------------------------
Release Note:
@nkeywal That is what I thought. Thanks for the clarification!!!
Another follow up question: how can you identify the AB problem ASAP? For
example, do you conclude that there is a AB when a running hbase application
read/write performance dramatically slow down? But sometimes, it could be just
a temporary issue and will recover after a while. Stop/start RS will just hurt
the performance due to region movement even with the MTTR improvement here.
Maybe simply just testing the performance for longer time before making
conclusion? Will that work? I am trying to see if there is any other better
ways to identify AB problem and use graceful_stop to help improve hbase cluster
performance.
Thanks.
> 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
