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 0E83B82AF for ; Thu, 18 Aug 2011 07:17:10 +0000 (UTC) Received: (qmail 9148 invoked by uid 500); 18 Aug 2011 07:17:08 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 8999 invoked by uid 500); 18 Aug 2011 07:16:59 -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 8984 invoked by uid 99); 18 Aug 2011 07:16:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Aug 2011 07:16:52 +0000 X-ASF-Spam-Status: No, hits=-2001.1 required=5.0 tests=ALL_TRUSTED,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, 18 Aug 2011 07:16:48 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 26363C167A for ; Thu, 18 Aug 2011 07:16:27 +0000 (UTC) Date: Thu, 18 Aug 2011 07:16:27 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: <1783372519.48175.1313651787136.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <380028256.48122.1313650167694.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-4224) Need a flush by regionserver rather than by table option 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-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086846#comment-13086846 ] stack commented on HBASE-4224: ------------------------------ An important bit I left off the top is that this 'flush by regionserver' needs to also clean up WAL logs too after the flushing is done. If everything has been flushed, then should be able to clean up any outstanding WAL logs. Scenario is the following. Your hosting service tells you that they are going to do a risky operation that could cause you to lose network connectivity or power to your racks. You know that a disaster may be coming and you want to mitigate the damage. A facility that flushed and cleaned up all WAL logs by the regionserver (so could throttle i/o) so if bad crash there is little to replay is what I'm talking about here. > Need a flush by regionserver rather than by table option > -------------------------------------------------------- > > Key: HBASE-4224 > URL: https://issues.apache.org/jira/browse/HBASE-4224 > Project: HBase > Issue Type: Bug > Components: shell > Reporter: stack > > This evening needed to clean out logs on the cluster. logs are by regionserver. to let go of logs, we need to have all edits emptied from memory. only flush is by table or region. We need to be able to flush the regionserver. Need to add this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira