[
https://issues.apache.org/jira/browse/CASSANDRA-10982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088967#comment-15088967
]
Sylvain Lebresne commented on CASSANDRA-10982:
----------------------------------------------
bq. Additionally, I don't think 10140 made it to trunk
Something is wrong with my git fu but I don't know what. According to the git
log, the patch from 3.0 _was_ properly merged but the changes somehow weren't
applied as if the merge was done with {{--strategy=ours}} even though I'm 100%
sure the merge was not done with that option. This is not the only patch that I
merge that had this problem in the last few days so if someone knows what I'm
doing wrong and can enlighten me, that would be highly appreciated. I did fix
this manually in the meantime.
> 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)
