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 70522183BA for ; Thu, 18 Feb 2016 03:33:19 +0000 (UTC) Received: (qmail 48493 invoked by uid 500); 18 Feb 2016 03:33:18 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 48239 invoked by uid 500); 18 Feb 2016 03:33:18 -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 48047 invoked by uid 99); 18 Feb 2016 03:33:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Feb 2016 03:33:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 8D6582C1F78 for ; Thu, 18 Feb 2016 03:33:18 +0000 (UTC) Date: Thu, 18 Feb 2016 03:33:18 +0000 (UTC) From: "Duo Zhang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-14949) Resolve name conflict when splitting if there are duplicated WAL entries 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-14949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-14949: ------------------------------ Attachment: HBASE-14949-v5.patch Docker build failed... Retry... > Resolve name conflict when splitting if there are duplicated WAL entries > ------------------------------------------------------------------------ > > Key: HBASE-14949 > URL: https://issues.apache.org/jira/browse/HBASE-14949 > Project: HBase > Issue Type: Sub-task > Reporter: Heng Chen > Assignee: Duo Zhang > Attachments: HBASE-14949-v3.patch, HBASE-14949-v4.patch, HBASE-14949-v5.patch, HBASE-14949.patch, HBASE-14949_v1.patch, HBASE-14949_v2.patch > > > The AsyncFSHLog introduced in HBASE-14790 may write same WAL entries to different WAL files. WAL entry itself is idempotent so replay is not a problem but the intermediate file name and final name when splitting is constructed using the lowest or highest sequence id of the WAL entries written, so it is possible that different WAL files will have same intermediate or final file name when splitting. In the currentm implementation, this will cause split fail or data loss. We need to solve this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)