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 4C08FC04E for ; Thu, 3 May 2012 20:11:15 +0000 (UTC) Received: (qmail 93306 invoked by uid 500); 3 May 2012 20:11:15 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 93256 invoked by uid 500); 3 May 2012 20:11: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 93058 invoked by uid 99); 3 May 2012 20:11:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2012 20:11:14 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2012 20:11:10 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 2645B42EC31 for ; Thu, 3 May 2012 20:10:48 +0000 (UTC) Date: Thu, 3 May 2012 20:10:48 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: issues@hbase.apache.org Message-ID: <1849497699.23571.1336075848158.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1828098152.23481.1336075009269.JavaMail.tomcat@hel.zones.apache.org> 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 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267765#comment-13267765 ] Lars Hofhansl commented on HBASE-5930: -------------------------------------- What should trigger the flush is an interesting discussion in itself. Should we flush: * after N timeunits of write inactivity, or * when the last flush happened more than N TUs ago The former would avoid smaller storefiles, the latter would put a limit on how stale an entry in the memstore can be. > Periodically flush the Memstore? > -------------------------------- > > Key: HBASE-5930 > URL: https://issues.apache.org/jira/browse/HBASE-5930 > Project: HBase > Issue Type: Improvement > Reporter: Lars Hofhansl > Priority: Minor > > 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira