HBASE-19797 Operator priority leads to wrong logic in ReplicationSourceWALReader
This commit is contained in:
parent
3b638f7ea1
commit
3a66f15557
|
@ -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());
|
||||
|
|
Loading…
Reference in New Issue