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 4E9181057B for ; Thu, 9 May 2013 03:49:20 +0000 (UTC) Received: (qmail 11953 invoked by uid 500); 9 May 2013 03:49:19 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 11700 invoked by uid 500); 9 May 2013 03:49: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 11444 invoked by uid 99); 9 May 2013 03:49:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 May 2013 03:49:17 +0000 Date: Thu, 9 May 2013 03:49:17 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8498) PB WAL reading is broken due to some partial reads 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-8498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652716#comment-13652716 ] stack commented on HBASE-8498: ------------------------------ [~sershe] Would life be easier if BaseDecoder took a DataInputStream rather than an InputStream? It is InputStream because want to do the LowestCommonDenominator but seeing your messing w/ EOF and given this the first use of Codec backed by a real stream, maybe we should change it up from IS to DIS? > PB WAL reading is broken due to some partial reads > -------------------------------------------------- > > Key: HBASE-8498 > URL: https://issues.apache.org/jira/browse/HBASE-8498 > Project: HBase > Issue Type: Bug > Reporter: Sergey Shelukhin > Assignee: Sergey Shelukhin > Priority: Critical > Attachments: HBASE-8498-v0.patch, HBASE-8498-v0.patch, HBASE-8498-v1.patch, HBASE-8498-v2.patch, HBASE-8498-v4.patch > > > From dev list, there's IOException during log splitting on hadoop-2.0.3. We need to understand whether this is caused by EOF, and ignore it if it is. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira