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
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
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:
lhid {
rhid1 : count
rhid2 : count
}
[...]
lhid {
count-rhid1 : PLACEHOLDER
count-rhid2 : PLACEHOLDER
}
would be a better way of
On 9 June 2010 09:53, Dr. Martin Grabmüller
martin.grabmuel...@eleven.de wrote:
Hi Jools,
what happens in Cassandra with your scenario is the following:
1) insert new record
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
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
that!
On Wed, Jun 2, 2010 at 3:15 PM, Dr. Martin Grabmüller
martin.grabmuel...@eleven.de 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
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
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.
