Ah! Thank you.
Explained better here:
http://www.slideshare.net/benjaminblack/introduction-to-cassandra-replication-and-consistency
On Tue, May 4, 2010 at 8:38 PM, Robert Coli wrote:
> On 5/4/10 7:16 AM, Jonathan Shook wrote:
>
>> I may be wrong here. Someone please correct me if I am.
>> ...
>>
On 5/4/10 7:16 AM, Jonathan Shook wrote:
I may be wrong here. Someone please correct me if I am.
...
The ability to set the replication factor on inserts and gets allows
you to decide when (if) and how much (little) to pay the price for
consistency.
You mean "Consistency Level", not "Replicati
I may be wrong here. Someone please correct me if I am.
There may be a race condition if you aren't increasing your replication
factor.
If you insert to node A with replication factor 1, and then get from node B
with replication factor 1, it should be possible (and even more likely in
uneven loadi
:) I think this is simpler and I am just stupid
I retried with clean data and commit log directories and everything works
well.
I should have missed something (maybe when I upgraded from 0.5.1 to 0.6) but
anyway, I am just in test.
On Tue, May 4, 2010 at 8:47 AM, Jonathan Shook wrote:
> I
I think you may found the "eventually" in eventually consistent. With a
replication factor of 1, you are allowing the client thread to continue to
the read on node#2 before it is replicated to node 2. Try setting your
replication factor higher for different results.
Jonathan
On Tue, May 4, 2010 a
Hi all,
I can't figure out how to deal with request routing...
In fact I have two nodes in the "Test Cluster" and I wrote the client as
specified here http://wiki.apache.org/cassandra/ThriftExamples#Java. The
Keyspace is the default one (KeySpace1, replicatorFactor 1..)
The Seeds are well configu
