[CASSANDRA-7090] Add ability to set/get logging levels to nodetool

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 2.0.8, 2.1 beta2
• Component/s: Tool/nodetool
• Assignee: Jackson Chung
• Reporter: Jackson Chung

Authors

Jackson Chung

Reviewers

Vijay

• Created: 25/Apr/14 01:14
• Updated: 16/Apr/19 09:31
• Resolved: 29/Apr/14 04:40

Description

While it is nice to use logback (per #CASSANDRA-5883) and with the autoreload feature, in some cases ops/admin may not have the permission or ability to modify the configuration file(s). Or the files are controlled by puppet/chef so it is not desirable to modify them manually.

There is already an existing operation for setLoggingLevel in the StorageServuceMBean , so that's easy to expose that to the nodetool

But what was lacking was ability to see the current log level settings for various loggers.

The attached diff aims to do 3 things:

1. add JMX getLoggingLevels --> return a map of current loggers and the corresponding levels
2. expose both getLoggingLevels and setLoggingLevel to nodetool. In particular, the setLoggingLevel behave as follows:
   • If both classQualifer and level are empty/null, it will reload the configuration to reset.
   • If classQualifer is not empty but level is empty/null, it will set the level to null for the defined classQualifer
   • The logback configuration should have < jmxConfigurator /> set

The diff is based on the master branch which uses logback, soit is not applicable to 2.0 or 1.2. (2.1 is ok) Though it would be nice to have the same ability for 2.0.