Philip Zeyliger created IMPALA-7441: ---------------------------------------
Summary: Java logging happens before Java logging is configured, leading to INFOs printed at ERROR Key: IMPALA-7441 URL: https://issues.apache.org/jira/browse/IMPALA-7441 Project: IMPALA Issue Type: Task Reporter: Philip Zeyliger The following is pretty surprising: {code} catalogd.....impala.log.ERROR.20180813-040536.9529:18/08/13 04:05:37 INFO util.JvmPauseMonitor: Starting JVM pause monitor {code} Namely, we've got an INFO-level log message appearing in the ERROR file. What's going on (I think) is that {{GlogAppender.Install()}} is being called during the constructors of Frontend and Catalog objects: {code} $git grep GlogAppender.Install fe/src/main/java/org/apache/impala/service/JniCatalog.java: GlogAppender.Install(TLogLevel.values()[cfg.impala_log_lvl], fe/src/main/java/org/apache/impala/service/JniFrontend.java: GlogAppender.Install(TLogLevel.values()[cfg.impala_log_lvl], {code} Meanwhile, the pause monitor is initialized earlier: {code} $git grep -C5 JniUtil::InitJvmPauseMonitor | head be/src/common/init.cc- if (!fs_cache_init_status.ok()) CLEAN_EXIT_WITH_ERROR(fs_cache_init_status.GetDetail()); be/src/common/init.cc- be/src/common/init.cc- if (init_jvm) { be/src/common/init.cc- ABORT_IF_ERROR(JniUtil::Init()); be/src/common/init.cc- InitJvmLoggingSupport(); be/src/common/init.cc: ABORT_IF_ERROR(JniUtil::InitJvmPauseMonitor()); be/src/common/init.cc- ZipUtil::InitJvm(); be/src/common/init.cc- } {code} This is largely cosmetic, but it was surprising to me. -- This message was sent by Atlassian JIRA (v7.6.3#76005)