trouble with deleted counter columns

Running a single 1.0.3 node and using counter columns I have a problem. I have rows with ~200k counters. I deleted a number of such rows and now I can't put counters back in, or really, I can't query what I put back in. Example using the cli: [default@rslog_production] get req_word_freq['2024'

Strategies to maintain counters sorted row ?

I know it is not possible to sort columns in a row by counter values so what are the other strategies to maintain a sorted list (of counters) in cassandra? Could you propose some schema that might be helpful to achieve this ? Or do I need to retrieve thousands of columns each time and do the sort

Re: Decommission a node causing high IO usage on 2 other nodes

Yes, we do have RF=3. That explains it all. Thanks Peter! Huy Peter Schuller wrote > >> What may be causing high IO wait on 2.new and 3.new? > > Do you have RF=3? > > The problem with 'nodetool ring' in terms of interpreting those '0%' > is that it does not take RF and replication strateg

Re: Yanking a dead node

Thanks! Looks pretty obvious in retrospect... Regards, Maxim On 11/24/2011 6:54 AM, Filipe Gonçalves wrote: Just remove its token from the ring using nodetool removetoken 2011/11/23 Maxim Potekhin: This was discussed a long time ago, but I need to know what's the state of the art answer to

How many indexes to keep? Guidelines

As a matter of practice, how many secondary indexes on a CF do you usually keep? What are rules of thumb? Is 10 too many? 100? 1000? Thanks Maxim

Re: Decommission a node causing high IO usage on 2 other nodes

> What may be causing high IO wait on 2.new and 3.new? Do you have RF=3? The problem with 'nodetool ring' in terms of interpreting those '0%' is that it does not take RF and replication strategy into account. If you have RF=3, whatever data has its primary range assigned to node N will also be on

Re: User Survey

Showing the system CF's such as hints, migrations and location info is not helpful to most. Although once or twice i have had fun poking around in them. Removing that might make 'show keyspaces' have smaller output. Edward On Tue, Nov 29, 2011 at 1:40 PM, Jeremy Hanna wrote: > > On Nov 29, 2011,

Re: User Survey

On Nov 29, 2011, at 12:25 PM, Don Smith wrote: > cli's "show keyspaces" command shows way too much information by default. > > I think by default it should show just one line per keyspace. A "-v" option > could show more info. If you are using 1.x, there is a describe command for specific ke

re: User Survey

cli's "show keyspaces" command shows way too much information by default. I think by default it should show just one line per keyspace. A "-v" option could show more info. What GUI alternatives are there to cli for browsing a cassandra ring? Lots of people WILL use cli, so it should be spif

Re: [RELEASE] Apache Cassandra 1.0.4 released

If it is not too late, please disregard this release for now.  It contains atleast two serious regression: CASSANDRA-3539 and CASSANDRA-3540.  Note thatthe latter will prevent you for starting node on 1.0.4 if you use secondaryindexes. None of those will cause data loss of any sort. We're working o

Re: upgrade to 1.0.4

On Tue, Nov 29, 2011 at 6:52 PM, Michael Vaknine wrote: > In cassandra.yaml I have this configured: > partitioner: org.apache.cassandra.dht.RandomPartitioner > > why has the partitioner changed? > Is this something I did? No, it is not something you did. This is a regression, more precisely: http

RE: upgrade to 1.0.4

In cassandra.yaml I have this configured: partitioner: org.apache.cassandra.dht.RandomPartitioner why has the partitioner changed? Is this something I did? Where can I find documentation on this topic. Thanks Michael -Original Message- From: Jonathan Ellis [mailto:jbel...@gmail.com] Se

Re: upgrade to 1.0.4

That looks like a regression caused by https://issues.apache.org/jira/browse/CASSANDRA-3407. We'll work on a fix ASAP; in the meantime, you should move back to 1.0.3. (No data loss has been caused.) On Tue, Nov 29, 2011 at 11:01 AM, Michael Vaknine wrote: > Hi, > Upgrade cluster 1.0.3 to 1.0.4

upgrade to 1.0.4

Hi, Upgrade cluster 1.0.3 to 1.0.4 gives me this errors. Can someone help me here? Many thanks, Michael TST-Cass1 ERROR [SSTableBatchOpen:1] 2011-11-29 16:52:08,044 at org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:143) TST-Cass1 ERROR [SSTableBatchOpen:1] 2011-11-29 16:52:

results of get_range_slice is ordered?

hi, I use the* **partitioner*: org.apache.cassandra.dht.ByteOrderedPartitioner for 4 different cassandra nodes. I use get_range_slice method and I want to know whether the results are *sorted by keys*? thanks

Re: Corrupt (negative) value length encountered

Didn't mention this is a 0.8.6 cluster with 5 nodes and RF=3 I bootstrapped a new node 2 days ago. What's weird is that it didn't pickup the token i provided in the yaml file so i had to move it. It looks like CASSANDRA-1992 but I'm not on 0.7.x Le 29 nov. 2011 08:00, "Philippe" a écrit : > Hello

Cassandra DataModeling recommendations

Hi all, In order to evaluate NoSQL solutions and to gain knowledge, I am currently working on a kind of prototype. Here is a brief overview of the scope: I would like to manage user carts. Lets keep things simple: A user can have up to n (lets say 3 for example) carts. Each cart will contain me

Re: commit log size

Ok, thanks! On Mon, Nov 28, 2011 at 8:53 PM, Jeremiah Jordan < jeremiah.jor...@morningstar.com> wrote: > Yes, the low volume memtables are causing the problem. Lower the > thresholds for those tables if you don't want the commit logs to go crazy. > > -Jeremiah > > > On 11/28/2011 11:11 AM, Alexa

[RELEASE] Apache Cassandra 1.0.4 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 1.0.4. Cassandra is a highly scalable second-generation distributed database, bringing together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model. You can read more here: http://cassand