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

HBASE-25570 On largish cluster, "CleanerChore: Could not delete dir..." makes master log unreadable (#2949) 

Turn down the amount we log. If you want to see the full exception
enable TRACE-level logging.

Signed-off-by: Duo Zhang <zhangduo@apache.org>
Signed-off-by: shahrs87
This commit is contained in:
Michael Stack 2021-03-11 21:35:24 -08:00 committed by GitHub
parent cc617140bf
commit 1a69a52653
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
hbase-server/src/main/java/org/apache/hadoop/hbase/master/cleaner/CleanerChore.java
View File

@ -468,9 +468,14 @@ public abstract class CleanerChore<T extends FileCleanerDelegate> extends Schedu
LOG.debug("Couldn't delete '{}' yet because it isn't empty w/exception.", dir, exception);
deleted = false;
} catch (IOException ioe) {
LOG.info("Could not delete {} under {}. might be transient; we'll retry. if it keeps "
+ "happening, use following exception when asking on mailing list.",
type, dir, ioe);
if (LOG.isTraceEnabled()) {
LOG.trace("Could not delete {} under {}; will retry. If it keeps happening, " +
"quote the exception when asking on mailing list.", type, dir, ioe);
} else {
LOG.info("Could not delete {} under {} because {}; will retry. If it keeps happening, enable" +
"TRACE-level logging and quote the exception when asking on mailing list.",
type, dir, ioe.getMessage());
}
deleted = false;
} catch (Exception e) {
LOG.info("unexpected exception: ", e);