cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8115) Windows install scripts fail to set logdir and datadir
Date Tue, 14 Oct 2014 19:59:34 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joshua McKenzie updated CASSANDRA-8115:
---------------------------------------
    Attachment: 8115_v1.txt

Passing in multiple semicolon delimited options to ++JvmOptions in procrunsrv is supposed
to work as documented [here|http://commons.apache.org/proper/commons-daemon/procrun.html],
however that is failing and is causing the errors that led to the creation of this ticket.

I've attached a v1 that tokenizes JAVA_OPTS and CASSANDRA_PARAMS and appends a ++JvmOptions=<param>
for each entry. Tested installation and running the service and it works on both legacy and
powershell paths, run from either the command prompt or powershell itself, from within a directory
that had a space in the name.

I also moved the logdir and storagedir declarations into the -env file and cleaned up the
quoting in the .bat file for the log and storage dir.

> Windows install scripts fail to set logdir and datadir
> ------------------------------------------------------
>
>                 Key: CASSANDRA-8115
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8115
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Joshua McKenzie
>            Assignee: Joshua McKenzie
>              Labels: Windows
>             Fix For: 2.1.1
>
>         Attachments: 8115_v1.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
(v6.3.4#6332)

Mime
View raw message