You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Murtadha Hubail (JIRA)" <ji...@apache.org> on 2016/01/30 07:59:39 UTC
[jira] [Updated] (ASTERIXDB-1283) Exceptions on stopping NCs are
not logged
[ https://issues.apache.org/jira/browse/ASTERIXDB-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Murtadha Hubail updated ASTERIXDB-1283:
---------------------------------------
Description: 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. (was: 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 detected invalid shutdown sequences.)
> 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: AsterixDB, Hyracks
> Reporter: 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
(v6.3.4#6332)