My bad, yes it does say dc2 in our config file (actually it is different ip
addresses and different names, but I wasn't sure if it
was sensitive information so changed it to generic terms).
Owen
On 5 December 2012 08:42, Tomas Nunez wrote:
>
>
> 2012/12/3 Owen Davies
>
>> cassandra-topology.pr
2012/12/3 Owen Davies
> cassandra-topology.properties
>
> 192.168.1.1=dc1:rack1
> 192.168.1.2=dc1:rack1
> 192.168.1.3=dc1:rack1
>
> 192.168.2.1=dc2:rack1
> 192.168.2.2=dc2:rack1
> 192.168.2.3=*dc3*:rack1
>
This is a typo, right? It says "dc2" in your
In our main application we are using local quorum to read. I realise
the default for cli is one, the point is that we want all our data on
all the servers, hence specifying [dc1:3, dc2:3] as the replication
strategy. After a couple of days we would expect it to have
replicated.
As I said, we will
> A few days after writing the data, we tried this on cassandra-cli
The default consistency level in the CLI is ONE, did you change it to LOCAL
QUOURM ?
(I'm assuming your example is for two reads from the same CF)
It looks like the first read was done at a lower CL, and the value returned is
We have written a large amount of data to Cassandra from another
database. When writing the client was set to write local quorum.
A few days after writing the data, we tried this on cassandra-cli
get example['key'][123];
Value was not found
Elapsed time: 50 msec(s).
Then a bit later
get datapoi
>>> When reading, sometimes the data is there,
>>> sometimes it is not, which we think is a replication issue, even
>>> though we have left it plenty of time after the writes.
Can you provide some more information on this ?
Are you talking about writes to one DC and reads from another ?
Cheers
Hi Shamim
I have read a bit about the Tokens. I understand how that could effect
the data distribution at first, but I don't understand if we have
specified Options: [dc1:3, dc2:3], surely after a while all the data
will be on every server?
Thanks,
Owen
On 3 December 2012 14:06, Шамим wrote:
>
