From 78602fc474d659a4c1ccdaed9f36b53ce49263fa Mon Sep 17 00:00:00 2001 From: zhangduo Date: Mon, 15 Jan 2018 15:20:13 +0800 Subject: [PATCH] HBASE-19797 Operator priority leads to wrong logic in ReplicationSourceWALReader --- .../hbase/replication/regionserver/ReplicationSourceWALReader.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceWALReader.java b/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceWALReader.java index e2201e5..90a421d 100644 --- a/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceWALReader.java +++ b/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceWALReader.java @@ -204,8 +204,8 @@ public class ReplicationSourceWALReader extends Thread { // (highly likely we've closed the current log), we've hit the max retries, and autorecovery is // enabled, then dump the log private void handleEofException(IOException e) { - if (e instanceof EOFException || - e.getCause() instanceof EOFException && logQueue.size() > 1 && this.eofAutoRecovery) { + if ((e instanceof EOFException || e.getCause() instanceof EOFException) && + logQueue.size() > 1 && this.eofAutoRecovery) { try { if (fs.getFileStatus(logQueue.peek()).getLen() == 0) { LOG.warn("Forcing removal of 0 length log in queue: " + logQueue.peek()); -- 2.7.4