[
https://issues.apache.org/jira/browse/CASSANDRA-10140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964026#comment-14964026
]
Ariel Weisberg edited comment on CASSANDRA-10140 at 10/19/15 8:48 PM:
----------------------------------------------------------------------
[~cnlwsu] I was going to update the 3.0 patch, but then I noticed that the
current gc logging directory is /var/log/cassandra, but in your patch you are
using $env:CASSANDRA_HOME/logs in some cases, but not in others even in the
same version of C*. Which is the correct path?
If it's a Windows vs Linux thing, well JVM options is now common to both in 3.0
so maybe the log path needs to be specified in cassandra-env for each platform?
was (Author: aweisberg):
[~cnlwsu] I was going to update the 3.0 patch, but then I noticed that the
current gc logging directory is /var/log/cassandra, but in your patch you are
using $env:CASSANDRA_HOME/logs in some cases, but not in others even in the
same version of C*. Which is the correct path?
> 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.txt,
> cassandra-2.2-10140-v2.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)
