RE: UnavailableException with 3 nodes and RF=2

When you write with QUORUM, RF/2+1 of the nodes cassandra *wants to write* to have to be up. In your case, RF/2+1 = 2, that means, the two nodes responsible for the write have to be up, not any two nodes. Each write which tries to the node with token 78502309573904554351249603414557542595 and

RE: skip + limit support in GetSlice

Have you considered creating a second column family which acts as an index for the original column family? Have the record number as the column name, and the value as the identifier (primary key) of the original data, and do a 1. get_slice(, start='00051235', finish='', limit=100) 2. get_slic

RE: UUIDs whose alphanumeric order is the same as their chronological order

You can use the sever's name/IP-address+Port and mix it into the random seed. Martin From: David Boxenhorn [mailto:da...@lookin2.com] Sent: Friday, June 25, 2010 10:14 AM To: user@cassandra.apache.org Subject: Re: UUIDs whose al

RE: Update vs Delete/Insert

Hi Colin, > From: Colin Vipurs [mailto:zodiac...@gmail.com] [...] > I've got some data that I'm doing counts on, stored in a CF as: > > { > : > : > > } [...] > { > : PLACEHOLDER > : PLACEHOLDER > } > > would be a better way of storing the data? Does anyone know t

RE: single node capacity

Your problem is probably not the amount of data you store, but the number of SSTable files. When these increase, read latency goes up. Write latency maybe goes up because of compaction. Check in the data directory, whether there are many data files, and check via JMX whether compaction is happe

RE: Inserting new data, where the key points to a tombstone record.

d ? --Jools On 9 June 2010 09:53, Dr. Martin Grabmüller wrote: Hi Jools, what happens in Cassandra with your scenario is the following: 1) insert new record ->

RE: Inserting new data, where the key points to a tombstone record.

Hi Jools, what happens in Cassandra with your scenario is the following: 1) insert new record -> the record is added to Cassandra's dataset (with the given timestamp) 2) delete record -> a tombstone is added to the data set (with the timestamp of the deletion, which should be larger

RE: Expected wait while bootstrapping?

The next time you encounter such a problem, check with JMX whether any compactions are pending on the sending node. Compaction and anticompaction are run in the same stage IIRC, so when a long-running compaction is in progress, all anticompaction on the same node has to wait. Martin > -Origi

RE: Range search on keys not working?

l try that! On Wed, Jun 2, 2010 at 3:15 PM, Dr. Martin Grabmüller wrote: When not using OOP, you should not use something like 'CATEGORY/' as the end key. Use the empty string as the end key and limit the number of r

RE: Range search on keys not working?

When not using OOP, you should not use something like 'CATEGORY/' as the end key. Use the empty string as the end key and limit the number of returned keys, as you did with the 'max' value. If I understand correctly, the end key is used to generate an end token by hashing it, and there is not

RE: trying to make my ideas clear about partionning...

Partitioning is only done for row keys, the part in your message about keys and partitioning is correct. There is no partitioning for columns, all columns for a particular key are stored on the same node (plus replicas, of course, which are stored on different nodes). The CompareWith option fo

RE: Strange streaming behaviour

t bootstrap has > completed normally, but when you check, it appears to be hung on the > receiving nodes? > > Do you mind turning debug on and and seeing if you can reproduce? The > strange part is that the source node doesn't think it's streaming at > all. >

RE: Appropriate use for Cassandra?

>http://www.youtube.com/watch?v=eaCCkfjPm0o > Thank you. You saved my day. Martin

Strange streaming behaviour

Hello list, I encountered a problem with streaming in my test cluster but found nothing like this in JIRA or on the list. I'm running a test cluster of three nodes, RF=3, Cassandra 0.6.1. I started the first node and inserted some data, then bootstrapped the other machines one after the other. N

RE: Periodically hiccups

Hello Alex, unfortunately I can not help with your problem, just one hint: > - RecentReadLatencyMicros and RecentWriteLatencyMicros are super high > for StorageProxy, as well as every column family in JMX: up > to 43 s and > 9s (see screenshot). However, in cfstats, they are quite small. Rem