You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2019/05/31 11:52:00 UTC
[jira] [Commented] (HBASE-22502) Purge the logs when we reach the
EOF for the last wal file when replication
[ https://issues.apache.org/jira/browse/HBASE-22502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852941#comment-16852941 ]
Hudson commented on HBASE-22502:
--------------------------------
Results for branch master
[build #1071 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1071/]: (x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/master/1071//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1071//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1071//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Purge the logs when we reach the EOF for the last wal file when replication
> ---------------------------------------------------------------------------
>
> Key: HBASE-22502
> URL: https://issues.apache.org/jira/browse/HBASE-22502
> Project: HBase
> Issue Type: Bug
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.3.0
>
>
> Now there will be strange a warn log
> {noformat}
> 2019-05-30 14:59:38,426 WARN [RS:1;zhangduo-ubuntu:39885.replicationSource.wal-reader.zhangduo-ubuntu%2C39885%2C1559199556433,2] wal.ProtobufLogReader(422): Encountered a malformed edit, seeking back to last good position in file, from 2459 to 2459
> java.io.EOFException: First byte is negative at offset 2459
> at org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader.readNext(ProtobufLogReader.java:347)
> at org.apache.hadoop.hbase.regionserver.wal.ReaderBase.next(ReaderBase.java:98)
> at org.apache.hadoop.hbase.regionserver.wal.ReaderBase.next(ReaderBase.java:86)
> at org.apache.hadoop.hbase.replication.regionserver.WALEntryStream.readNextEntryAndRecordReaderPosition(WALEntryStream.java:263)
> at org.apache.hadoop.hbase.replication.regionserver.WALEntryStream.tryAdvanceEntry(WALEntryStream.java:176)
> at org.apache.hadoop.hbase.replication.regionserver.WALEntryStream.hasNext(WALEntryStream.java:101)
> at org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.readWALEntries(ReplicationSourceWALReader.java:195)
> at org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.run(ReplicationSourceWALReader.java:138)
> {noformat}
> And in TestReplicationStatus* UTs, we set the retry interval to 100ms, so the logs are flooded with these useless warns...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)