Re: [PR] Shutdown log to flush async log before bookie exit [bookkeeper]

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

AnonHxy commented on PR #4475:
URL: https://github.com/apache/bookkeeper/pull/4475#issuecomment-2254399639

   > What happens if the user doesn't include logs4j's jars and uses logback or something else? All prod components of BK should only depend on slf4j.
   
   Good point.  But it seems that there is no way to shutdown or force flush the log through slf4j api.  So some log will be lost if user using async logger appender.
   
   I think that we could print the key error logs to `stderr`.  So that users can  find cause for abnormal exit from the termianl  or stderr logs.    @dlg99 @shoothzj 


-- 
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