In this case it's a cluster in a test environment we set up while
experimenting with cassandra.
Bram
On Wed, Sep 3, 2014 at 5:07 PM, Robert Coli wrote:
> On Wed, Sep 3, 2014 at 1:36 PM, Bram Avontuur
> wrote:
>
>> Ok, that seems right. Doesn't look too bad, but I'll keep an eye on it.
>> Than
On Wed, Sep 3, 2014 at 1:36 PM, Bram Avontuur
wrote:
> Ok, that seems right. Doesn't look too bad, but I'll keep an eye on it.
> Thanks.
>
I feel obligated to say that RF=N=2 is an unusual and probably degenerate
configuration of Cassandra I have never heard of people operating before.
There are
Ok, that seems right. Doesn't look too bad, but I'll keep an eye on it.
Thanks.
On Tue, Sep 2, 2014 at 5:43 PM, DuyHai Doan wrote:
> Hello Bram
>
> You're probably running into this :
> https://issues.apache.org/jira/browse/CASSANDRA-4417
>
> It's marked as won't fix because it is related to th
Hello Bram
You're probably running into this :
https://issues.apache.org/jira/browse/CASSANDRA-4417
It's marked as won't fix because it is related to the current counter
design. Fortunately C* 2.1 will fix this.
Worth reading :
www.datastax.com/dev/blog/whats-new-in-cassandra-2-1-a-better-implem
Hi,
Cassandra setup:
* 2 nodes on EC2, m1.large
* Cassandra version 2.0.10
One node died over the weekend, and I couldn't revive it. I deleted it with
nodetool removenode, and added a new node with a copy of the cassandra.yaml
config with the ip addresses changed.
Once reconfigured and starte
