Re: 0.7RC1 cassandra-env.sh or cassandra.in.sh?

The double JVM option was a side effect of https://issues.apache.org/jira/browse/CASSANDRA-1771 and will be addressed with the next release. The rpm uses the cassandra.in.sh from the debian directory for convenience. The instance of cassandra-env.sh in /usr/share/cassandra/conf is kept as a refere

Re: 0.7RC1 cassandra-env.sh or cassandra.in.sh?

The rpm I'm using is: http://rpm.riptano.com/EL/6/x86_64/cassandra07-0.7.0-0rc1.el6.noarch.rpm. Yes, seems like a bug. I created CASSANDRA-1808 . Thanks, -Thor On Dec 2, 2010, at 2:42 PM, Nick Bailey wrote: They should be set in cassandra

Re: 0.7RC1 cassandra-env.sh or cassandra.in.sh?

They should be set in cassandra-env.sh. Did you build the rpm yourself using the spec file in the source? If so its probably a bug. If not where did you get the rpm file from? On Thu, Dec 2, 2010 at 4:07 PM, Thor Carpenter wrote: > Hi All, > > After installing 0.7RC1 RPM on CentOS and starting th

0.7RC1 cassandra-env.sh or cassandra.in.sh?

Hi All, After installing 0.7RC1 RPM on CentOS and starting the cassandra service I am confused by the presence of duplicate and conflicting JVM params. There seem to be multiple places where JVM_OPTS are set. Is this a known issue? Any recommendations? Thanks! -Thor # find / -name cassandra