You've had people on this list tell you you should upgrade off such an old release at least twice already this month.
The reason we do this is, the odds are good that the answer is "someone else ran into that problem a year ago and it got fixed." Personally, I don't think it's worth the time to troubleshoot before upgrading. Re compaction and repair, you can read up on both at http://www.datastax.com/docs/0.8/operations/scheduled_tasks. On Tue, May 17, 2011 at 1:30 PM, Ali Ahsan <ali.ah...@panasiangroup.com> wrote: > Hi All, > > I was diagnosing high CPU usage on my Cassandra 0.6.3.Then i came across > Cassandra wiki link which suggested following. > > > " > > To lower compaction priority (thus reducing its impact on the rest of the > system, and making it take longer), add these options to cassandra.in.sh in > 0.6.3 or later: > > -XX:+UseThreadPriorities \ > -XX:ThreadPriorityPolicy=42 \ > -Dcassandra.compaction.priority=1 \ > > " > > http://wiki.apache.org/cassandra/PerformanceTuning > > > After adding above in my cassandra.in.sh my high CPU usage seems to dropped > very very low in fact it seem nothing is running on machine's. > > So here is my question do i need to run nodetool compact or not and what > about noretool rapier. > > -- > S.Ali Ahsan > > > > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
