Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-19797 Operator priority leads to wrong logic in ReplicationSourceWALReader

This commit is contained in:
zhangduo 2018-01-15 15:20:13 +08:00
parent 204a4539c4
commit e014e5f8ef
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceWALReader.java
View File

@ -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 // (highly likely we've closed the current log), we've hit the max retries, and autorecovery is
// enabled, then dump the log // enabled, then dump the log
private void handleEofException(IOException e) { private void handleEofException(IOException e) {
if (e instanceof EOFException || if ((e instanceof EOFException || e.getCause() instanceof EOFException) &&
e.getCause() instanceof EOFException && logQueue.size() > 1 && this.eofAutoRecovery) { logQueue.size() > 1 && this.eofAutoRecovery) {
try { try {
if (fs.getFileStatus(logQueue.peek()).getLen() == 0) { if (fs.getFileStatus(logQueue.peek()).getLen() == 0) {
LOG.warn("Forcing removal of 0 length log in queue: " + logQueue.peek()); LOG.warn("Forcing removal of 0 length log in queue: " + logQueue.peek());