[jira] [Updated] (CASSANDRA-7999) Inconsistent logging in CassandraDaemon
[ https://issues.apache.org/jira/browse/CASSANDRA-7999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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 (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-7999) Inconsistent logging in CassandraDaemon
[ https://issues.apache.org/jira/browse/CASSANDRA-7999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaun Kalley updated CASSANDRA-7999: Description: 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 upgrades to fatal. (was: 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.) > 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 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 upgrades to fatal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-7999) Inconsistent logging in CassandraDaemon
[ https://issues.apache.org/jira/browse/CASSANDRA-7999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaun Kalley updated CASSANDRA-7999: Description: 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. (was: 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 upgrades to fatal.) > 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 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 (v6.3.4#6332)
