Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 584BC10C96 for ; Fri, 10 Jan 2014 19:49:51 +0000 (UTC) Received: (qmail 24181 invoked by uid 500); 10 Jan 2014 19:49:51 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 24149 invoked by uid 500); 10 Jan 2014 19:49:51 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 24140 invoked by uid 99); 10 Jan 2014 19:49:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jan 2014 19:49:51 +0000 Date: Fri, 10 Jan 2014 19:49:51 +0000 (UTC) From: "Keith Turner (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-2172) Concurrent compactions before machine failure may cause uneeded recovery 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/ACCUMULO-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Turner updated ACCUMULO-2172: ----------------------------------- Affects Version/s: 1.5.0 seems this is an issue in 1.5.0 also. Looked at 1.4.5-SNAP and its syncs these events. > Concurrent compactions before machine failure may cause uneeded recovery > ------------------------------------------------------------------------ > > Key: ACCUMULO-2172 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2172 > Project: Accumulo > Issue Type: Bug > Affects Versions: 1.5.0 > Reporter: Keith Turner > Fix For: 1.5.1, 1.6.0 > > > [~vines] noticed that minc finish events are not synced to the walog. I was looking into this issue to see if it was a problem and I noticed a possible issue w/ this. If the following sequence of events occurs, its possible that duplicate recovery may occur. > # Tablet T1 writes File F1 to metadata table after minor compaction > # T1 write minc finish event to walog (no sync is done and info not in walog) > # T1 adds F1 to set of files in tablets memory > # T1 major compacts F1 into F2 > # Tablet server serving T1 fails (and nothing synced walog) > # T1 recovers data in F1 because there is no finish event or file in metadata table > Step 2 must sync before step 3, because step 3 makes the file eligible for major compaction. Its seems like the sync could be done using group commit for efficiency. -- This message was sent by Atlassian JIRA (v6.1.5#6160)