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 31ED9200B87 for ; Mon, 19 Sep 2016 21:38:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 30693160ACC; Mon, 19 Sep 2016 19:38:23 +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 9BE94160ABB for ; Mon, 19 Sep 2016 21:38:22 +0200 (CEST) Received: (qmail 62733 invoked by uid 500); 19 Sep 2016 19:38:21 -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 62717 invoked by uid 99); 19 Sep 2016 19:38:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Sep 2016 19:38:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 868492C1B77 for ; Mon, 19 Sep 2016 19:38:21 +0000 (UTC) Date: Mon, 19 Sep 2016 19:38:21 +0000 (UTC) From: "Sean Busbey (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-15984) Given failure to parse a given WAL that was closed cleanly, replay the WAL. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 19 Sep 2016 19:38:23 -0000 [ https://issues.apache.org/jira/browse/HBASE-15984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504436#comment-15504436 ] Sean Busbey commented on HBASE-15984: ------------------------------------- Since we're talking about data loss, I originally wanted to push this for all branches. I'm fine leaving out the metrics additions on maintenance release lines if folks prefer, but I've always interpreted the operational section of the compatibility promises as saying we wouldn't remove metrics in a maintenance release rather than that we wouldn't add them. > Given failure to parse a given WAL that was closed cleanly, replay the WAL. > --------------------------------------------------------------------------- > > Key: HBASE-15984 > URL: https://issues.apache.org/jira/browse/HBASE-15984 > Project: HBase > Issue Type: Sub-task > Components: Replication > Reporter: Sean Busbey > Assignee: Sean Busbey > Priority: Critical > Fix For: 2.0.0, 1.0.4, 1.4.0, 1.3.1, 1.1.7, 0.98.23, 1.2.4 > > Attachments: HBASE-15984.1.patch, HBASE-15984.2.patch > > > subtask for a general work around for "underlying reader failed / is in a bad state" just for the case where a WAL 1) was closed cleanly and 2) we can tell that our current offset ought not be the end of parseable entries. -- This message was sent by Atlassian JIRA (v6.3.4#6332)