Re: [I] [Question] Changing log levels for autorecovery on connection failure to bookies [bookkeeper]

["lhotari (via GitHub)" <gi...@apache.org>]

lhotari commented on issue #4679:
URL: https://github.com/apache/bookkeeper/issues/4679#issuecomment-5573376993

   Related: I have opened #4878 for the `DefaultBookieAddressResolver` INFO line specifically (the first line in your sample output).
   
   Short version: that message is logged unconditionally at the throw site, immediately before throwing `BookieIdNotResolvedException`, and callers such as `TopologyAwareEnsemblePlacementPolicy.resolveNetworkLocation()` catch it and recover silently. So the resolver logs every occurrence while the code that handled it logs nothing, and the volume is bounded only by the call rate. It has been raised before in #2285, partly addressed in #2538, and PR #4113 proposed making the level configurable but was closed unmerged.
   
   Your ERROR lines from `PerChannelBookieClient` and `ReplicationWorker` are a separate concern from that one, so it seemed cleaner to track the resolver logging on its own issue rather than take this question off course.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bookkeeper.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org