[
https://issues.apache.org/jira/browse/ASTERIXDB-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327303#comment-16327303
]
Michael Blow commented on ASTERIXDB-1283:
-----------------------------------------
We should visit how to solve this now that we've adopted log4j2.
Starting in Log4j 2.6, you can now use
{{org.apache.logging.log4j.LogManager.shutdown()}} to initiate shutdown
manually, if shutdownHook="disable" is specified on the config. We should take
care to only shutdown after both CC and NC have completed shutting down.
> Exceptions on stopping NCs are not logged
> -----------------------------------------
>
> Key: ASTERIXDB-1283
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1283
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: *DB - AsterixDB, HYR - Hyracks
> Reporter: Murtadha Hubail
> Assignee: Murtadha Hubail
> Priority: Minor
>
> Currently we use Java Logger to log messages and exceptions while stopping
> NodeControllerService in JVMShutdownHook. Those messages and exceptions are
> not logged because the JVM will disable all registered loggers with the
> LogManager before the JVMShutdownHook thread completes execution. Logging
> those exceptions is important to detect invalid shutdown sequences.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
