cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8115) Windows install scripts fail to set logdir and datadir
Date Thu, 23 Oct 2014 22:00:34 GMT


Joshua McKenzie commented on CASSANDRA-8115:

bq. However, I'm not required to quote all arguments when running cassandra.bat through powershell,
but not through command prompt.

I'm going to assume you meant that powershell requires quotation marks and command-prompt
doesn't.  It looks like PowerShell is finicky about arguments with a '.' in them.  If you
pass something bogus (say, cassandrajoin_ring instead of cassandra.join_ring) with the -s
flag you can see that it passes it correctly.

Looks like PowerShell tokenizing arguments on period is [a thing|].

With that being said, you +1 on the _fix patch [~philipthompson]?

> Windows install scripts fail to set logdir and datadir
> ------------------------------------------------------
>                 Key: CASSANDRA-8115
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Joshua McKenzie
>            Assignee: Joshua McKenzie
>              Labels: Windows
>             Fix For: 2.1.2
>         Attachments: 8115_fix.txt, 8115_v1.txt, 8115_v2.txt
> After CASSANDRA-7136, the install scripts to run Cassandra as a service fail on both
the legacy and the powershell paths.  Looks like they need to have
> {code}
> ++JvmOptions=-Dcassandra.logdir=%CASSANDRA_HOME%\logs ^
> ++JvmOptions=-Dcassandra.storagedir=%CASSANDRA_HOME%\data
> {code}
> added to function correctly.
> We should take this opportunity to make sure the source of the java options is uniform
for both running and installation to prevent mismatches like this in the future.

This message was sent by Atlassian JIRA

View raw message