[CASSANDRA-6170] Modify AbstractCassandraDaemon.initLog4j() to allow for hotfixing log level on on a cassandra class

• Type: New Feature
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.2.11, 2.0.2
• Component/s: Local/Config
• Assignee: Brandon Williams
• Reporter: Darla Baker

Authors

Brandon Williams

Reviewers

Aleksey Yeschenko

• Created: 09/Oct/13 00:58
• Updated: 16/Apr/19 09:32
• Resolved: 14/Oct/13 21:39

Description

When customer wants to bump up log level of a cassandra class, here is the procedure they follow:

1. Add the class name and log level to log4j-server.properties into a revision identified directory.
2. The new directory is then symbolically linked to the location where cassandra looks for that directory.

However cassandra and it's log4j continue to watch the old location

The reason for this AbstractCassandraDaemon.initLog4j() uses this

configFileName = new File(configLocation.toURI()).getCanonicalPath();

The customer believes if we change that to the following, this will allow the symlink to work properly.

configFileName = new File(configLocation.toURI()).getPath();

If it were possible to add a configuration that would invoke this change on "True" that would be ideal. Or find another method to allow hotfixing the log4j changes.