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 at 12:14 AM, Olivier Mallassi <omalla...@octo.com>wrote: > 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 configured (using the IP) : ie. the cassandra log > indicates that the servers are up. > > <http://wiki.apache.org/cassandra/ThriftExamples#Java>Everything goes > well if I write and read the data on node#1 for instance. Yet, if I write > the data on node#1 and then read the same data (using the key) on node#2, > no data is found. > > Did I miss something? > As far as I understood, I should be able to reach any nodes from the > cluster and the node should be able to "redirect" the request to the "good" > node > > Thank you for your answers and your time. > > Best Regards. > > Olivier. > > -- > ............................................................ > Olivier Mallassi > OCTO Technology > ............................................................ > 50, Avenue des Champs-Elysées > 75008 Paris > > Mobile: (33) 6 28 70 26 61 > Tél: (33) 1 58 56 10 00 > Fax: (33) 1 58 56 10 01 > > http://www.octo.com > Octo Talks! http://blog.octo.com > > >
