Cassandra commitlog directory size increase on every restart - Cassandra 1.1.0

2012-08-08 Thread Kasun Weranga
Hi all, I am facing the above issue in Cassandra 1.1.0, it will add 134.2MB commitlog file in every restart, but it never delete it. We can't control the commitlog dir size even by explicitly setting commitlog_total_space_in_mb in cassandra.yaml. I set commitlog_total_space_in_mb as 512 in

Cassandra 1.0 - is disk seek required to access SSTable metadata

2012-08-08 Thread Maciej Miklas
Hi all, older Cassandra versions had to read columns from each SSTable with positive bloom filter in order to find recent value. This was optimized with: Improve read performance in update-intensive workload https://issues.apache.org/jira/browse/CASSANDRA-2498 Now each SSTable has metadata -

Re: Unreachable node, not in nodetool ring

2012-08-08 Thread Alain RODRIGUEZ
Hi, I finally successfully removed the ghost node using unsafeAssassinateEndpoint() as described there : http://tumblr.doki-pen.org/post/22654515359/assinating-cassandra-nodes, I hope this can help more people. Nodetool gossipinfo gives me now the following info for the ghost node :

Re: Use of SSD for commitlog

2012-08-08 Thread Hiller, Dean
Probably not since it is sequential writes….(ie. Seek performance is the big hit and if it is sequential it should not be seeking and is about just as fast as an SSD in theory). In practice, I have not measure the performance of one vs. the other though…that I always the best way to go.(you

lost keyspace

2012-08-08 Thread Arend-Jan Wijtzes
Hi, Today we rebooted a node in our cluster for maintenance and after that one of the keyspaces went missing. This is what we did leading up to this: nodetool drain -h localhost reboot restart cassandra There was an error during startup: ERROR [MutationStage:109] 2012-08-08 14:05:56,443

Re: Use of SSD for commitlog

2012-08-08 Thread Darvin Denmian
Thanks for your reply Dean, considering your reply maybe I use a 15k RPM SCSI Disk, I think it'll perform better than a SSD disk. On Wed, Aug 8, 2012 at 10:01 AM, Hiller, Dean dean.hil...@nrel.gov wrote: Probably not since it is sequential writes….(ie. Seek performance is the big hit and

Re: Use of SSD for commitlog

2012-08-08 Thread Hiller, Dean
A 7.5 is probably fine and can still beat it as it is going to be the speed of writing not seeking(and I am not sure if they spec hard drives with a write time when not seeking….not sure). Remember that drives are rated on how fast they spin…this disk should not be spinning a lot(in theory)…it

Re: Use of SSD for commitlog

2012-08-08 Thread Amit Kumar
There is a really good presentation about SSD and Cassandra on youtube by Rick Branson. I highly recommend watching it. http://www.youtube.com/watch?v=zQdDi9pdf3I Amit On Aug 8, 2012, at 6:23 AM, Hiller, Dean wrote: A 7.5 is probably fine and can still beat it as it is going to be the speed

Re: lost keyspace

2012-08-08 Thread Arend-Jan Wijtzes
Forgot to mention that the keyspace 'twitter' was created, then droppend and re-created a couple of days ago. How about if I create a new keyspace with the same definition and then copy the existing tables into the proper place and call nodetool refresh on each node. Would that work or are there

Re: lost keyspace

2012-08-08 Thread Mateusz Korniak
On Wednesday 08 of August 2012, Arend-Jan Wijtzes wrote: Forgot to mention that the keyspace 'twitter' was created, then droppend and re-created a couple of days ago. How about if I create a new keyspace with the same definition and then copy the existing tables into the proper place and

Re: Use of SSD for commitlog

2012-08-08 Thread Darvin Denmian
Great ! On Wed, Aug 8, 2012 at 11:41 AM, Amit Kumar kumaramit.ex...@gmail.comwrote: There is a really good presentation about SSD and Cassandra on youtube by Rick Branson. I highly recommend watching it. http://www.youtube.com/watch?v=zQdDi9pdf3I Amit On Aug 8, 2012, at 6:23 AM, Hiller,

Re: change cluster name

2012-08-08 Thread Tim Dunphy
Hello, Thanks for your replies. DNS seems to be properly configured: [root@beta:~] #host beta.jokefire.com beta.jokefire.com has address 198.101.216.47 And I forgot the step to use the nodetool flush command. Taking it from the top again: [default@unknown] use system; Authenticated to

Re: lost keyspace

2012-08-08 Thread Arend-Jan Wijtzes
On Wed, Aug 08, 2012 at 05:08:56PM +0200, Mateusz Korniak wrote: On Wednesday 08 of August 2012, Arend-Jan Wijtzes wrote: Forgot to mention that the keyspace 'twitter' was created, then droppend and re-created a couple of days ago. How about if I create a new keyspace with the same

Re: change cluster name

2012-08-08 Thread Abhijit Chanda
If you have used the above commands then i guess problem lies in this step. [default@system] set LocationInfo[utf8('L')][utf8('*Test Cluster*')]=utf8('Jokefire Cluster'); It should be like this: set LocationInfo[utf8('L')][utf8('Cluster Name')]=utf8('Jokefire Cluster');

Re: change cluster name

2012-08-08 Thread Tim Dunphy
whoops! sorry about that! trying again.. [default@unknown] connect beta.jokefire.com/9160; Connected to: Test Cluster on beta.jokefire.com/9160 [default@unknown] use system; Authenticated to keyspace: system [default@system] set LocationInfo[utf8('L')][utf8('Cluster Name')]=utf8('Jokefire

Re: Use of SSD for commitlog

2012-08-08 Thread Terje Marthinussen
Probably you can get an intel 320 160GB or a Samsung 830 for the same price as the 146GB 15k rpm drive. Overprovision the SSD 20% and off you go. It will beat the HDD both sequentially and randomly. Terje On Aug 8, 2012, at 11:41 PM, Amit Kumar kumaramit.ex...@gmail.com wrote: There is a

Re: change cluster name

2012-08-08 Thread Abhijit Chanda
Hey Tim, Can you repeat these steps as given below? I guess now you are missing step no 6. Start the Cassandra-cli connected to your node. Run the following: 1. use system; 2. set LocationInfo[utf8('L')][utf8('ClusterName')]=utf8('Brisk Cluster'); 3. exit; 4. Run nodetool

Re: change cluster name

2012-08-08 Thread Tim Dunphy
Hi Abhijit, Thanks and actually I did restart cassandra at the end. I suspect I will have to delete the files in my system keyspace folder. I'm not at liberty to do that at the moment, but I will give that shot as soon as I'm able. Thank you again Tim On Wed, Aug 8, 2012 at 12:24 PM, Abhijit

Re: How to purge the Hinted data from Cassandra 1.0.11

2012-08-08 Thread Roshan
I managed to delete the hints from JConsole by using HintedHadOffManager MBean. Thanks. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/How-to-purge-the-Hinted-data-from-Cassandra-1-0-11-tp7581614p7581641.html Sent from the

Syncing nodes + Cassandra Data Availability

2012-08-08 Thread Ben Kaehne
Good morning, Our application runs on a 3 node cassandra cluster with RF of 3. We use quorum operations against this cluster in hopes of garunteeing consistency. One scenario in which an issue can occur here is: Out of our 3 nodes, only 2 are up. We perform a write to say, a new key. The down

Re: change cluster name

2012-08-08 Thread rajesh.ba...@orkash.com
Hi Tim, I had a similar problem and I sorted it out in the following manner. The cluster name is stored in two places. In he cassandra.yaml and the system keyspace. Everytime you start a node it checks the cluster name in both these places. If changes in the configuration files is not working