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

Jonathan Ellis resolved CASSANDRA-1808.
---------------------------------------

    Resolution: Not A Problem

ah, it means that the rpm Thor is using was generated with an older spec file.

> Duplicate JVM_OPTS set in RPM
> -----------------------------
>
>                 Key: CASSANDRA-1808
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1808
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>    Affects Versions: 0.7.0 rc 1
>         Environment: CentOS 5.4 and RPM found here: 
> http://rpm.riptano.com/EL/6/x86_64/cassandra07-0.7.0-0rc1.el6.noarch.rpm
>            Reporter: Thor Carpenter
>            Assignee: Nick Bailey
>            Priority: Minor
>
> 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.  Executing find on clean 
> install reveals multiple files that set JVM_OPTS.  According to the mailing 
> list, the correct file is cassandra-env.sh although which one is unclear.  It 
> would be less confusing if this redundancy was removed.
> For Reference:
> > find / -name cassandra*.sh
> /etc/cassandra/cassandra-env.sh
> /usr/share/cassandra/conf/cassandra-env.sh
> /usr/share/cassandra/cassandra.in.sh
> > ps aux | grep cassandra
> 100       8881 51.5 54.0 620988 135616 ?       Sl   21:55   0:02 
> /usr/bin/java -Xdebug *-Xms128M -Xmx1G* -XX:TargetSurvivorRatio=90 
> -XX:+AggressiveOpts -XX:+UseParNewGC -XX:+UseConcMarkSweepGC 
> -XX:+CMSParallelRemarkEnabled -XX:+HeapDumpOnOutOfMemoryError 
> -XX:SurvivorRatio=128 -XX:MaxTenuringThreshold=0 
> -Dcom.sun.management.jmxremote.port=8080 
> -Dcom.sun.management.jmxremote.ssl=false 
> -Dcom.sun.management.jmxremote.authenticate=false -ea 
> -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 *-Xms122M -Xmx122M* 
> -XX:+HeapDumpOnOutOfMemoryError -Xss128k -XX:+UseParNewGC 
> -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8 
> -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75 
> -XX:+UseCMSInitiatingOccupancyOnly -Djava.net.preferIPv4Stack=true 
> -Dcom.sun.management.jmxremote.port=8080 
> -Dcom.sun.management.jmxremote.ssl=false 
> -Dcom.sun.management.jmxremote.authenticate=false 
> -Dlog4j.configuration=log4j-server.properties 
> -Dcassandra-pidfile=/var/run/cassandra/cassandra.pid -cp 
> /etc/cassandra:/usr/share/cassandra/antlr-3.1.3.jar:/usr/share/cassandra/apache-cassandra-0.7.0-rc1-SNAPSHOT.jar:/usr/share/cassandra/apache-cassandra.jar:/usr/share/cassandra/avro-1.4.0-fixes.jar:/usr/share/cassandra/avro-1.4.0-sources-fixes.jar:/usr/share/cassandra/commons-cli-1.1.jar:/usr/share/cassandra/commons-codec-1.2.jar:/usr/share/cassandra/commons-collections-3.2.1.jar:/usr/share/cassandra/commons-lang-2.4.jar:/usr/share/cassandra/concurrentlinkedhashmap-lru-1.1.jar:/usr/share/cassandra/guava-r05.jar:/usr/share/cassandra/high-scale-lib.jar:/usr/share/cassandra/jackson-core-asl-1.4.0.jar:/usr/share/cassandra/jackson-mapper-asl-1.4.0.jar:/usr/share/cassandra/jetty-6.1.21.jar:/usr/share/cassandra/jetty-util-6.1.21.jar:/usr/share/cassandra/jline-0.9.94.jar:/usr/share/cassandra/json-simple-1.1.jar:/usr/share/cassandra/jug-2.0.0.jar:/usr/share/cassandra/libthrift-0.5.jar:/usr/share/cassandra/log4j-1.2.16.jar:/usr/share/cassandra/servlet-api-2.5-20081211.jar:/usr/share/cassandra/slf4j-api-1.6.1.jar:/usr/share/cassandra/slf4j-log4j12-1.6.1.jar:/usr/share/cassandra/snakeyaml-1.6.jar
>  org.apache.cassandra.thrift.CassandraDaemon

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to