C. Scott Andreas updated CASSANDRA-7999:
    Component/s: Testing

> Inconsistent logging in CassandraDaemon
> ---------------------------------------
>                 Key: CASSANDRA-7999
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7999
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Testing
>            Reporter: Shaun Kalley
>            Priority: Minor
> Both fatal and non-fatal errors are being 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 upgraded to fatal.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to