You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Shaun Kalley (JIRA)" <ji...@apache.org> on 2014/09/24 18:47:13 UTC

[jira] [Created] (CASSANDRA-7999) Inconsistent logging in CassandraDaemon

Shaun Kalley created CASSANDRA-7999:
---------------------------------------

             Summary: Inconsistent logging in CassandraDaemon
                 Key: CASSANDRA-7999
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7999
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
            Reporter: Shaun Kalley
            Priority: Minor


Both fatal and non-fatal errors are bring logged at error level which creates a problem for monitoring.  CassandraDaemon.setup() logs an error-level message if a directory does not exist but is still able to continue if the directory can be created, and CassandraDaemon.activate() logs an error-level message if the MBean cannot be registered but still allows the server to start.  I'd like to see the logging levels for these issues downgraded to warning, or the levels for the fatal errors upgrades to fatal.



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