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 821971145C for ; Fri, 18 Apr 2014 15:45:22 +0000 (UTC) Received: (qmail 74490 invoked by uid 500); 18 Apr 2014 15:45:17 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 74453 invoked by uid 500); 18 Apr 2014 15:45:17 -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 74436 invoked by uid 99); 18 Apr 2014 15:45:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Apr 2014 15:45:16 +0000 Date: Fri, 18 Apr 2014 15:45:16 +0000 (UTC) From: "Tianying Chang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-10935) support snapshot policy where flush memstore can be skipped to prevent production cluster freeze 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-10935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974171#comment-13974171 ] Tianying Chang commented on HBASE-10935: ---------------------------------------- This should be fine, I can change to that. And when not putting this extra parameter of {SKIP_FLUSH }, the default behavior is still original FLUSH for backward compatibility. Sounds good? > support snapshot policy where flush memstore can be skipped to prevent production cluster freeze > ------------------------------------------------------------------------------------------------ > > Key: HBASE-10935 > URL: https://issues.apache.org/jira/browse/HBASE-10935 > Project: HBase > Issue Type: New Feature > Components: shell, snapshots > Affects Versions: 0.94.7, 0.94.18 > Reporter: Tianying Chang > Assignee: Tianying Chang > Priority: Minor > Fix For: 0.94.20 > > Attachments: HBase-10935.patch > > > We are using snapshot feature to do HBase disaster recovery. We will do snapshot in our production cluster periodically. The current flush snapshot policy require all regions of the table to coordinate to prevent write and do flush at the same time. Since we use WALPlayer to complete the data that is not in the snapshot HFile, we don't need the snapshot to do coordinated flush. The snapshot just recored all the HFile that are already there. > I added the parameter in the HBase shell. So people can choose to use the NoFlush snapshot when they need, like below. Otherwise, the default flush snpahot support is not impacted. > >snaphot 'TestTable', 'TestSnapshot', 'skipFlush' -- This message was sent by Atlassian JIRA (v6.2#6252)