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 D9F2018153 for ; Fri, 12 Feb 2016 05:18:18 +0000 (UTC) Received: (qmail 72349 invoked by uid 500); 12 Feb 2016 05:18:18 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 72267 invoked by uid 500); 12 Feb 2016 05:18: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 72168 invoked by uid 99); 12 Feb 2016 05:18:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Feb 2016 05:18:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 3C8492C1F68 for ; Fri, 12 Feb 2016 05:18:18 +0000 (UTC) Date: Fri, 12 Feb 2016 05:18:18 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-15252) Data loss when replaying wal if HDFS timeout 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-15252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144073#comment-15144073 ] Ted Yu commented on HBASE-15252: -------------------------------- Test failures don't seen to be related to patch. +1 > Data loss when replaying wal if HDFS timeout > -------------------------------------------- > > Key: HBASE-15252 > URL: https://issues.apache.org/jira/browse/HBASE-15252 > Project: HBase > Issue Type: Bug > Components: wal > Affects Versions: 2.0.0, 1.2.0, 1.3.0, 1.0.3, 1.1.3, 0.98.17 > Reporter: Duo Zhang > Assignee: Duo Zhang > Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.4, 1.0.4, 0.98.18 > > Attachments: HBASE-15252-testcase.patch, HBASE-15252-v1.patch, HBASE-15252.patch > > > This is a problem introduced by HBASE-13825 where we change the exception type in catch block in {{readNext}} method of {{ProtobufLogReader}}. > {code:title=ProtobufLogReader.java} > try { > ...... > ProtobufUtil.mergeFrom(builder, new LimitInputStream(this.inputStream, size), > (int)size); > } catch (IOException ipbe) { // <------ used to be InvalidProtocolBufferException > throw (EOFException) new EOFException("Invalid PB, EOF? Ignoring; originalPosition=" + > originalPosition + ", currentPosition=" + this.inputStream.getPos() + > ", messageSize=" + size + ", currentAvailable=" + available).initCause(ipbe); > } > {code} > Here if the {{inputStream}} throws an {{IOException}} due to timeout or something, we just convert it to an {{EOFException}} and at the bottom of this method, we ignore {{EOFException}} and return false. This cause the upper layer think we reach the end of file. So when replaying we will treat the HDFS timeout error as a normal end of file and cause data loss. -- This message was sent by Atlassian JIRA (v6.3.4#6332)