Hi,
We are testing Cassandra and tried to remove a node from the cluster using
nodetool decomission. The node transferred the data, then "died" for about
20 minutes without responding, then came back to life with a load of
50-100, was in a heavy load during about 1 hour and then returned to normal
ve each
> node manually a token before adding data. There are a few messages in
> multiple threads related to this, so I suspect it's very common and I hope
> it's gone with 0.7.
>
> Thibaut
>
>
>
>
>
> On Sun, Nov 7, 2010 at 6:57 PM, Marc Canaleta wrote:
>
Hi,
Did you solve this problem? I'm having the same poblem. I'm trying to
bootstrap a third node in a 0.66 cluster. It has two keyspaces: Keyspace1
and KeyspaceLogs, both with replication factor 2.
It starts bootstrapping, receives some streams but it keeps waiting for
streams. I enabled the debu
What do you mean by "running live"? I am also planning to use cassandra on
EC2 using small nodes. Small nodes have 1/4 cpu of the large ones, 1/4 cost,
but I/O is more than 1/4 (amazon does not give explicit I/O numbers...), so
I think 4 small instances should perform better than 1 large one (and t
Hi!
I like the new feature of making live schema updates. You can add, drop and
rename columns and keyspaces via thrift, but how do you modify column
attributes like key_cache_size or rows_cached?
Thank you.
