Fix async log appender not print error log when bookie starting expectionally

[AnonHxy]

Motivation

Fix #4474

The root cause is that when bookie starting error, the java runtime will exit immediately. And the log4j can not shutdown gracefully:

bookkeeper/bookkeeper-server/src/main/java/org/apache/bookkeeper/server/Main.java

Lines 199 to 201 in e5c418e

	public static void main(String[] args) {
	int retCode = doMain(args);
	Runtime.getRuntime().exit(retCode);

Changes

Call LogManager#shutdown in jvm shutdown hook.

[shoothzj]

IIUC, you mean call LogManager#shutdown will flush the log to the disk?

[dlg99]

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.

[AnonHxy]

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

[AnonHxy]

rerun failure checks

[shoothzj]

Thank you for the update. I understand the need to ensure logs are flushed properly. However, adding multiple System.err outputs might not be the most elegant solution. Could we consider pushing for adding this hook to log4j2 instead?

BTW, I am trying to fix the ci in #4476