Issue 2531 - Fix noisy stacktrace at boot (#2532)
### Motivation
The exception is managed with a fallback, printing the stacktrace would be misleading
### Changes
- Changed log level from info to debug for the log line
- Removed the exception from the log line
Master Issue: #2531
diff --git a/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/DefaultBookieAddressResolver.java b/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/DefaultBookieAddressResolver.java
index 3a7636f..d11eaa9 100644
--- a/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/DefaultBookieAddressResolver.java
+++ b/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/DefaultBookieAddressResolver.java
@@ -56,7 +56,7 @@
return res;
} catch (BKException.BKBookieHandleNotAvailableException ex) {
if (BookieSocketAddress.isDummyBookieIdForHostname(bookieId)) {
- log.info("Resolving dummy bookie Id {} using legacy bookie resolver", bookieId, ex);
+ log.debug("Resolving dummy bookie Id {} using legacy bookie resolver", bookieId);
return BookieSocketAddress.resolveDummyBookieId(bookieId);
}
log.info("Cannot resolve {}, bookie is unknown", bookieId, ex);