[
https://issues.apache.org/jira/browse/CASSANDRA-21804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Konstantinov updated CASSANDRA-21804:
--------------------------------------------
Fix Version/s: 4.0.x
4.1.x
5.0.x
6.0.x
7.x
> cassandra-env.sh may fail if Cassandra directory path contains Xmx, Xms or
> Xmn
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-21804
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21804
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Local/Scripts
> Reporter: Dmitry Konstantinov
> Assignee: Dmitry Konstantinov
> Priority: Normal
> Labels: green_ci
> Fix For: 4.0.x, 4.1.x, 5.0.x, 6.0.x, 7.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> cassandra-env.sh decides whether heap flags were set with plain substring
> searches: echo $JVM_OPTS | grep -q Xmx and grep -q Xms
> (conf/cassandra-env.sh:89-92 on trunk). Xmx matches the path and Xms doesn't,
> so it prints "Please set or unset -Xmx and -Xms flags in pairs" and exits 1
> For example, we may get "run-python-dtest.XmxjVU/" directory as a part of our
> DTest. ccm rewrites each node's GC logging option to an absolute path
> (<node>/logs/gc.log). So the directory name ends up in JVM_OPTS.
> As a result we get a cryptic error from ccm that it cannot find a Cassandra
> PID after an startup.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
