You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/05/20 23:39:12 UTC

[jira] [Commented] (ASTERIXDB-1460) Global logger level is not respected until Hyracks application starts

    [ https://issues.apache.org/jira/browse/ASTERIXDB-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294535#comment-15294535 ] 

ASF subversion and git services commented on ASTERIXDB-1460:
------------------------------------------------------------

Commit fa51d428372965603406c2498f7316cea4b895be in incubator-asterixdb's branch refs/heads/master from [~imaxon]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-asterixdb.git;h=fa51d42 ]

ASTERIXDB-1460: Fix log level crashing CC on start

The Hyracks CC would nullpoint on startup if the log level was
greater than FINEST. This works around the core issue that's in
ASTERIXDB-1460 since in this instance the way the log level was used
would cause the CC to fail on startup where the log level was
equal to or greater than FINEST.

Change-Id: I720eca41fac312fc6cbdbb880162a5bc8b0357dc
Reviewed-on: https://asterix-gerrit.ics.uci.edu/870
Reviewed-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Murtadha Hubail <hu...@gmail.com>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>


> Global logger level is not respected until Hyracks application starts
> ---------------------------------------------------------------------
>
>                 Key: ASTERIXDB-1460
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1460
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: Murtadha Hubail
>            Priority: Minor
>
> The global log level that is read from asterix-configuration.xml file is not set until applicationStart() is called on Cluster/NodeControllerService. Any Logger operation before that will be based on the default Logger level value (INFO). To avoid this, the global logger level need to be set at the beginning of the CC/NC process start up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)