Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5D3FC200B7E for ; Wed, 7 Sep 2016 00:00:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5C169160ACE; Tue, 6 Sep 2016 22:00:25 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C9E7B160AA9 for ; Wed, 7 Sep 2016 00:00:24 +0200 (CEST) Received: (qmail 44052 invoked by uid 500); 6 Sep 2016 22:00:23 -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 44028 invoked by uid 99); 6 Sep 2016 22:00:23 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Sep 2016 22:00:23 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AC82B2C1B79 for ; Tue, 6 Sep 2016 22:00:23 +0000 (UTC) Date: Tue, 6 Sep 2016 22:00:23 +0000 (UTC) From: "Appy (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-16524) Clean procedure wal periodically instead of on every sync MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 06 Sep 2016 22:00:25 -0000 [ https://issues.apache.org/jira/browse/HBASE-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468754#comment-15468754 ] Appy commented on HBASE-16524: ------------------------------ Thinking about it, that should be easy to do. In our current logic, we basically do this: 1. make a copy of current global tracker, say T. 2. Iterate over log files: - keep the file if contain an update to proc P which is not marked deleted in T. - Delete P from T so we don't hold another older log file because of it. We can simply add step 0, which marks all recently updated procs as deleted in T. Sounds good? > Clean procedure wal periodically instead of on every sync > --------------------------------------------------------- > > Key: HBASE-16524 > URL: https://issues.apache.org/jira/browse/HBASE-16524 > Project: HBase > Issue Type: Bug > Reporter: Appy > Assignee: Appy > Priority: Minor > Attachments: HBASE-16524.master.001.patch, flame1.svg > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)