I would guess that means you've only configured a single replica per row.
On Sat, Jul 30, 2011 at 7:25 PM, Jason Baker wrote:
> When I run nodetool repair on a node on my 3-node cluster, I see 3 messages
> like the following:
> INFO [manual-repair-6d9a617f-c496-4744-9002-a56909b83d5b] 2011-07-30
thanks,Sorin It works!
haitong
On Fri, Jul 29, 2011 at 5:28 PM, Sorin Julean wrote:
> Hey,
>
> Try: echo *-e* "connnet localhost/9160;* \n*show keyspace*;*" |
> bin/cassandra-cli
>
> Regards,
> Sorin
>
>
> On Fri, Jul 29, 2011 at 9:54 AM, 祝海通 wrote:
>
>> In our Cassandra test for YCSB benchm
When I run nodetool repair on a node on my 3-node cluster, I see 3 messages
like the following:
INFO [manual-repair-6d9a617f-c496-4744-9002-a56909b83d5b] 2011-07-30
18:50:28,464 AntiEntropyService.java (line 636) No neighbors to repair with
for system on (0,56713727820156410577229101238628035242]
Hello,
I have computers that are better than others in my cluster. In special, there's
one which is much better and I'd like to give it more load than the others. Is
it
possible? I'm using RandomPartitioner, should I use other? Should I select
tokens
in some particular way? How is load distribut
On Saturday, July 30, 2011, Amresh Singh wrote:
> We are happy to announce release of Kundera 2.0.2
>
>
> Kundera is a JPA 2.0 compliant, Object-Datastore Mapping Library for
> NoSQL Datastores. The idea behind Kundera is to make working with
> NoSQL Databases drop-dead simple and fun. It currentl
We are happy to announce release of Kundera 2.0.2
Kundera is a JPA 2.0 compliant, Object-Datastore Mapping Library for NoSQL
Datastores. The idea behind Kundera is to make working with NoSQL Databases
drop-dead simple and fun. It currently supports Cassandra, HBase and
MongoDB. New features added
read_repair_chance: Probability (0.0-1.0) with which to perform read repairs
on CL.ONE reads
Default is 1.0 your CL.ONE reads will trigger read repairs for all reads.
You can update your column families definition to reduce that chance. For
the CL.ALL writes you can consider turning it off by sett
Hello,
I have a 3-node ring at RF=3 that is doing reads & writes. I am using two
types of consistency levels.
- write ALL,read ONE for one set of column families
- write QUORUM, read ONE for another set of families
Every day, I have a cron job that runs a nodetool repair on each node. The
n
