For tracking delay in very recent versions, this exists:
https://issues.apache.org/jira/browse/CASSANDRA-13289
--
Jeff Jirsa
> On Jul 11, 2018, at 1:05 AM, Simon Fontana Oscarsson
> wrote:
>
> I thought you just wanted to test how big delay you have, that's why I
> suggested trace.
>
>
I thought you just wanted to test how big delay you have, that's why I
suggested trace.
Your best option is to write with EACH_QUORUM as Alain said.
That way you will get a response when the write is successful on all dcs.
The downside is that the request will fail if one dc is down.
As usual it'
Simon,Trace would be significant burden on the cluster and it has to be on all
the time. I am trying to find a way to know when a row is written on demand
basis, is there a way to determine that? Naidu Saladi
On Tuesday, July 10, 2018 2:24 AM, Simon Fontana Oscarsson
wrote:
Have you
Alain,Thanks for the response and I completely agree with you about your
approach but there is a small caveat, we have another DC in Europe, right now
this keyspace is not replicating there but eventually will be added. EU DC has
significant latency of 200 ms RTT, so going with EACH_QUORUM would
Hello,
I have multi DC (3 DC's) Cassandra cluster/ring - One of the application
> wrote a row to DC1(using Local Quorum) and within span of 50 ms, it tried
> to read same row from DC2 and could not find the row.
[...]
So how to determine when the row is actually written in each DC?
To me, t
Have you tried trace?
--
SIMON FONTANA OSCARSSON
Software Developer
Ericsson
Ölandsgatan 1
37133 Karlskrona, Sweden
simon.fontana.oscars...@ericsson.com
www.ericsson.com
On mån, 2018-07-09 at 19:30 +, Saladi Naidu wrote:
> Cassandra is an eventual consistent DB, how to find when a row is act
Cassandra is an eventual consistent DB, how to find when a row is actually
written in multi DC environment? Here is the problem I am trying to solve
- I have multi DC (3 DC's) Cassandra cluster/ring - One of the application
wrote a row to DC1(using Local Quorum) and within span of 50 ms, it tri
