[
https://issues.apache.org/jira/browse/HBASE-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802229#comment-13802229
]
stack commented on HBASE-5843:
------------------------------
I went over your old SU MTTR doc [~nkeywal] I like the consideration given to
the general topic. Do you think we should start up another effort to go to the
next level w/ MTTR? For example, you mention cold-standbys in that old doc.
There are also other efforts that would help such as the off-heap zk session
pinging or getting distributed log replay so we can enable it as default, work
to make read/writes during WAL replay faster (more slots), bringing regions
online for writes immediately, more aggressive cleanup of outstanding WALs so
less to split on crash, etc.
Good on you [~nkeywal]
> 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.95.2
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Fix For: 0.96.0
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
