[
https://issues.apache.org/jira/browse/CASSANDRA-10982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089360#comment-15089360
]
Chris Lohfink commented on CASSANDRA-10982:
-------------------------------------------
Per conversation in irc. Not sure this ticket is possible since you cannot set
the -Xloggc jvm option to a system property. We ultimately set cassandra.logdir
to CASSANDRA_HOME/logs (except with deb patch) so this may be just unfortunate
chicken and egg thing requiring a little duplication.
> Put gc.log in -Dcassandra.logdir location by default
> ----------------------------------------------------
>
> Key: CASSANDRA-10982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10982
> Project: Cassandra
> Issue Type: Bug
> Components: Configuration
> Reporter: Philip Thompson
> Fix For: 2.2.x, 3.0.x, 3.x
>
>
> CASSANDRA-10140 turned on gc.log by default, and set it's location to
> CASSANDRA_HOME/logs. It would be much better UX if when -Dcassandra.logdir
> was set, that it was used instead. This way users don't have to separately
> configure gc.log from the other log files.
> Additionally, I don't think 10140 made it to trunk, as grepping for `loggc`
> there shows me nothing in cassandra-env.sh as of 31f67c289.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
