Hi,
As you are writing as CL.ONE and cqlsh by default reads at CL.ONE, there is
a probability that you are reading stale data i.e. the node you have
contacted for the read may not have the most recent data. If you have a
higher consistency requirement, you should look at increasing your
consistenc
On Tue, Aug 19, 2014 at 4:14 PM, Check Peck wrote:
> What could be the reason for this sync issue? Can anyone shed some light
> on this?
>
> Since our java driver code and datastax c++ driver code are using these
> tables with CONSISTENCY LEVEL ONE.
>
1) write with CL.ONE
2) get success respons
We have cassandra cluster in three different datacenters (DC1, DC2 and DC3)
and we have 10 machines in each datacenter. We have few tables in cassandra
in which we have less than 100 records.
What we are seeing - some tables are out of sync between machines in DC3 as
compared to DC1 or DC2 when we
> In other words, if one of the nodes is down - the write (or read) will fail.
No.
Cassandra will always try to get a write distributed to RF nodes. The
Consistency Level is how many replicas you want to be written before you accept
the request was a success. e.g. with RF 3 and QUORUM you are s
So what you're saying is that no matter what consistency level I'm using,
the data will be written to all CF nodes right away, the consistency level
is just for making sure that all CF nodes are UP and all data is written.
In other words, if one of the nodes is down - the write (or read) will fail.
Not sure I understand your question exactly, but will take a shot…
Writes are sent to every UP node, the consistency level is how many nodes we
require to complete before we say the request completed successfully. So we
also make sure that CL nodes are UP before we start the request. If you run
Is consistency level "All" for write actually grenty that my data is updated
in all of my node?
is it apply to read actions as-well?
I've read it on the wiki, I just want to make sure.
Thanks!
