Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C7389D9EF for ; Tue, 16 Oct 2012 00:07:04 +0000 (UTC) Received: (qmail 34660 invoked by uid 500); 16 Oct 2012 00:07:04 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 34456 invoked by uid 500); 16 Oct 2012 00:07:04 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 34446 invoked by uid 99); 16 Oct 2012 00:07:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Oct 2012 00:07:04 +0000 Date: Tue, 16 Oct 2012 00:07:04 +0000 (UTC) From: "Gregory Chanan (JIRA)" To: issues@hbase.apache.org Message-ID: <1665142121.48718.1350346024565.JavaMail.jiratomcat@arcas> In-Reply-To: <731942684.9256.1334918023596.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-5843) Improve HBase MTTR - Mean Time To Recover MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476590#comment-13476590 ] Gregory Chanan commented on HBASE-5843: --------------------------------------- bq. No / ~Yes. There's a maximum number of log files before a flush however. Not sure what you mean here. Are the rows the same or not? Are there are just more flushes on the 10M case? Thanks for clarifying. > 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