cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-11949) GC log directory should be created in startup scripts
Date Sun, 05 Feb 2017 16:45:42 GMT


Aleksey Yeschenko updated CASSANDRA-11949:
    Fix Version/s:     (was: 3.0.x)
                       (was: 2.2.x)
                       (was: 3.x)

> GC log directory should be created in startup scripts
> -----------------------------------------------------
>                 Key: CASSANDRA-11949
>                 URL:
>             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
> The default GC log path is set to {{$CASSANDRA_HOME/logs/gc.log}} in {{}},
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

View raw message