[
https://issues.apache.org/jira/browse/CASSANDRA-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505889#comment-14505889
]
Andrey commented on CASSANDRA-9084:
-----------------------------------
Let's setup different logging configuration for development with proper DEBUG
and TRACE appenders if it is required.
The summarized rationale:
* normally it is very easy to find where log message was generated based on
class name and message itself
* when it comes to deep debugging in production I would assume increasing log
level to DEBUG or TRACE rather than add line numbers.
* it's hard to always control whether new log message fits into critical path.
Critical paths might include: compaction stats/GC logs/repair &etc.
* I will never know in advance on what hardware and under what load cassandra
will be running. So I would assume create default configuration as performant
as possible. Even it's not on critical path.
> Do not generate line number in logs
> -----------------------------------
>
> Key: CASSANDRA-9084
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9084
> Project: Cassandra
> Issue Type: Improvement
> Components: Config
> Reporter: Andrey
> Assignee: Benedict
> Priority: Minor
>
> According to logback documentation
> (http://logback.qos.ch/manual/layouts.html):
> {code}
> Generating the line number information is not particularly fast. Thus, its
> use should be avoided unless execution speed is not an issue.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
