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 22010E691 for ; Wed, 6 Feb 2013 18:17:16 +0000 (UTC) Received: (qmail 55829 invoked by uid 500); 6 Feb 2013 18:17:15 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 55795 invoked by uid 500); 6 Feb 2013 18:17:15 -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 55785 invoked by uid 99); 6 Feb 2013 18:17:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2013 18:17:15 +0000 Date: Wed, 6 Feb 2013 18:17:15 +0000 (UTC) From: "Devaraj Das (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-5930) Periodically flush the Memstore? 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-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572632#comment-13572632 ] Devaraj Das commented on HBASE-5930: ------------------------------------ I should add that making the checks as described before prevents some potentially unneeded flushes, while bounding the max duration an edit lives in the memstore... [~lhofhansl], could you please take a look at the patch. > Periodically flush the Memstore? > -------------------------------- > > Key: HBASE-5930 > URL: https://issues.apache.org/jira/browse/HBASE-5930 > Project: HBase > Issue Type: Improvement > Reporter: Lars Hofhansl > Assignee: Devaraj Das > Priority: Minor > Fix For: 0.96.0 > > Attachments: 5930-1.patch, 5930-2.1.patch, 5930-2.2.patch, 5930-2.3.patch, 5930-wip.patch > > > A colleague of mine ran into an interesting issue. > He inserted some data with the WAL disabled, which happened to fit in the aggregate Memstores memory. > Two weeks later he a had problem with the HDFS cluster, which caused the region servers to abort. He found that his data was lost. Looking at the log we found that the Memstores were not flushed at all during these two weeks. > Should we have an option to flush memstores periodically. There are obvious downsides to this, like many small storefiles, etc. -- 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