[
https://issues.apache.org/jira/browse/CASSANDRA-11949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353220#comment-15353220
]
Joshua McKenzie commented on CASSANDRA-11949:
---------------------------------------------
bq. it requires me to run some command to enable some policy in the PowerShell
console to be able to create the directory
The PowerShell startup scripts require you set your execution policy to
unrestricted. See:
[link|https://technet.microsoft.com/en-us/library/hh847748.aspx]. Theoretically
we could limit the scope of the required security access by using
[Unblock-File|https://technet.microsoft.com/en-us/library/hh849924.aspx], but
then we'd have to swap to RemoteSigned on systems that default to Restricted,
etc. Ultimately, just don't run unknown powershell scripts on the user account
you're using to run C* on Windows and you're in good shape.
> 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)
