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 BD838101A7 for ; Thu, 25 Apr 2013 17:36:18 +0000 (UTC) Received: (qmail 91317 invoked by uid 500); 25 Apr 2013 17:36:18 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 91276 invoked by uid 500); 25 Apr 2013 17:36:18 -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 91267 invoked by uid 99); 25 Apr 2013 17:36:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Apr 2013 17:36:18 +0000 Date: Thu, 25 Apr 2013 17:36:18 +0000 (UTC) From: "ramkrishna.s.vasudevan (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=13641987#comment-13641987 ] ramkrishna.s.vasudevan commented on HBASE-5930: ----------------------------------------------- +1 on the Lars 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.95.1 > > Attachments: 5930-1.patch, 5930-2.1.patch, 5930-2.2.patch, 5930-2.3.patch, 5930-2.4.patch, 5930-track-oldest-sample.txt, 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