You do seem to be experiencing a problem indeed, but hard to say what it is
from just this (could be anything from a configuration problem, a cassandra
bug or a bug in the java driver).
But since you seem to be able to reproduce easily, if you can provide a
script that reproduce that issue, I'd gla
So, I have added more logging to the test app (comments inline). For
some reason I'm loosing updates. In a for loop I'm executing upload,
read writetime, download blob. Executed 10 times... See iteration number
2 and 3
1. initialize session
0[main] INFO com.datastax.driver.core.Clus
Hi Sylvain,
thanks for fast answer. I have updated keyspace definition and
cassandra-topologies.properties to all 3 nodes and restarted each node.
Both problems are still reproducible. I'm not able to read my writes and
also the selects shows same data as in my previous email.
for write and
Without looking into details too closely, I'd say you're probably hitting
https://issues.apache.org/jira/browse/CASSANDRA-5292 (since you use
NTS+propertyFileSnitch+a DC name in caps).
Long story short, the CREATE KEYSPACE interpret your DC-TORONTO as
dc-toronto, which then probably don't match wh
