[
https://issues.apache.org/jira/browse/CASSANDRA-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802649#comment-13802649
]
Mck SembWever commented on CASSANDRA-5883:
------------------------------------------
No, most people don't log that much. But it's nice to know that you can, if you
have to, turn all loggers to DEBUG, or even TRACE, in production without
hurting performance. With old-log4j and logback this often isn't possible.
The performance isn't an across the board improvement, as far as i've
understood it, but just an improvement that comes from removing all the little
contentions from synchronised blocks. I can imagine that this appeals to the c*
community, even if it's of little practical meaning for normal production c*
Log4j2 also provides the auto-reload of configuration files. Other features it
offers is at http://logging.apache.org/log4j/2.x/
> Switch to Logback
> -----------------
>
> Key: CASSANDRA-5883
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5883
> Project: Cassandra
> Issue Type: Improvement
> Components: Core, Tools
> Reporter: Jonathan Ellis
> Assignee: Dave Brosius
> Priority: Minor
> Fix For: 2.1
>
> Attachments: 0001-Additional-migration-to-logback.patch, 5883-1.txt,
> 5883-additional1.txt, 5883.txt
>
>
> Logback has a number of advantages over log4j, and switching will be
> straightforward since we are already using the slf4j translation layer:
> http://logback.qos.ch/reasonsToSwitch.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
