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 46CE8F4C4 for ; Wed, 8 May 2013 00:47:16 +0000 (UTC) Received: (qmail 70252 invoked by uid 500); 8 May 2013 00:47:16 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 70168 invoked by uid 500); 8 May 2013 00:47:15 -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 70153 invoked by uid 99); 8 May 2013 00:47:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 May 2013 00:47:15 +0000 Date: Wed, 8 May 2013 00:47:15 +0000 (UTC) From: "Jean-Daniel Cryans (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8253) A corrupted log blocked ReplicationSource 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-8253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651501#comment-13651501 ] Jean-Daniel Cryans commented on HBASE-8253: ------------------------------------------- Oh I see what you mean, I thought the problem was somehow caused by replay. So, unless I'm mistaken, the edit was then written into the next log and durability was ensured? So we just need to skip over this one? Thanks [~jeason] and sorry for being a bit slow. > A corrupted log blocked ReplicationSource > ----------------------------------------- > > Key: HBASE-8253 > URL: https://issues.apache.org/jira/browse/HBASE-8253 > Project: HBase > Issue Type: Bug > Components: Replication > Affects Versions: 0.94.6 > Reporter: Jieshan Bean > Assignee: Jieshan Bean > Attachments: HBASE-8253-94.patch > > > A writting log got corrupted when we forcely power down one node. Only partial of last WALEdit was written into that log. And that log was not the last one in replication queue. > ReplicationSource was blocked under this scenario. A lot of logs like below were printed: > {noformat} > 2013-03-30 06:53:48,628 WARN [regionserver26003-EventThread.replicationSource,1] 1 Got: org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:334) > java.io.EOFException: hdfs://hacluster/hbase/.logs/master11,26003,1364530862620/master11%2C26003%2C1364530862620.1364553936510, entryStart=40434738, pos=40450048, end=40450048, edit=0 > at sun.reflect.GeneratedConstructorAccessor42.newInstance(Unknown Source) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.addFileInfoToException(SequenceFileLogReader.java:295) > at org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.next(SequenceFileLogReader.java:240) > at org.apache.hadoop.hbase.replication.regionserver.ReplicationHLogReaderManager.readNextAndSetPosition(ReplicationHLogReaderManager.java:84) > at org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.readAllEntriesToReplicateOrNextFile(ReplicationSource.java:412) > at org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:330) > Caused by: java.io.EOFException > at java.io.DataInputStream.readFully(DataInputStream.java:180) > at org.apache.hadoop.io.DataOutputBuffer$Buffer.write(DataOutputBuffer.java:68) > at org.apache.hadoop.io.DataOutputBuffer.write(DataOutputBuffer.java:106) > at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:2282) > at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:2181) > at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:2227) > at org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.next(SequenceFileLogReader.java:238) > ... 3 more > .......... > 2013-03-30 06:54:38,899 WARN [regionserver26003-EventThread.replicationSource,1] 1 Got: org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:334) > java.io.EOFException: hdfs://hacluster/hbase/.logs/master11,26003,1364530862620/master11%2C26003%2C1364530862620.1364553936510, entryStart=40434738, pos=40450048, end=40450048, edit=0 > at sun.reflect.GeneratedConstructorAccessor42.newInstance(Unknown Source) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.addFileInfoToException(SequenceFileLogReader.java:295) > at org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.next(SequenceFileLogReader.java:240) > at org.apache.hadoop.hbase.replication.regionserver.ReplicationHLogReaderManager.readNextAndSetPosition(ReplicationHLogReaderManager.java:84) > at org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.readAllEntriesToReplicateOrNextFile(ReplicationSource.java:412) > at org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:330) > Caused by: java.io.EOFException > at java.io.DataInputStream.readFully(DataInputStream.java:180) > at org.apache.hadoop.io.DataOutputBuffer$Buffer.write(DataOutputBuffer.java:68) > at org.apache.hadoop.io.DataOutputBuffer.write(DataOutputBuffer.java:106) > at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:2282) > at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:2181) > at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:2227) > at org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.next(SequenceFileLogReader.java:238) > ... 3 more > ........... > {noformat} -- 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