[
https://issues.apache.org/jira/browse/CASSANDRA-10140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967739#comment-14967739
]
Ariel Weisberg commented on CASSANDRA-10140:
--------------------------------------------
[~cnlwsu] can you set it to patch available? I updated both the 2.2 and 3.0
patches to address the issues with CASSANDRA_HOME not being consistently used.
3.0 now integrates with the jvm.options file.
> Enable GC logging by default
> ----------------------------
>
> Key: CASSANDRA-10140
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10140
> Project: Cassandra
> Issue Type: Improvement
> Components: Config
> Reporter: Chris Lohfink
> Assignee: Chris Lohfink
> Priority: Minor
> Fix For: 2.2.x, 3.0.x
>
> Attachments: CASSANDRA-10140-2-2.txt, CASSANDRA-10140-v2.txt,
> CASSANDRA-10140.txt, cassandra-2.2-10140-v2.txt, cassandra-2.2-10140-v3.txt
>
>
> Overhead for the gc logging is very small (with cycling logs in 7+) and it
> provides a ton of useful information. This will open up more for C*
> diagnostic tools to provide feedback as well without requiring restarts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
