[ https://issues.apache.org/jira/browse/CASSANDRA-11949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua McKenzie updated CASSANDRA-11949: ---------------------------------------- Reviewer: Joshua McKenzie > GC log directory should be created in startup scripts > ----------------------------------------------------- > > Key: CASSANDRA-11949 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11949 > Project: Cassandra > Issue Type: Bug > Reporter: Joel Knighton > Assignee: Mahdi Mohammadi > Priority: Minor > > In [CASSANDRA-10140], we enabled GC logging by default, since the overhead > was low and asking people providing diagnostics to restart can often make it > more difficult to diagnose problems. > The default GC log path is set to {{$CASSANDRA_HOME/logs/gc.log}} in > {{cassandra-env.sh}}, a directory that is not present in a fresh > clone/install. Even if logback creates this directory later in startup, it is > not present when the JVM initiates GC logging, so GC logging will silently > fail for this first Cassandra run > I haven't tested this in Windows but suspect the same problem may occur. > Since lots of tooling around Cassandra won't create this directory, we should > instead consider attempting to create it in our startup scripts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)