assandra.apache.org>
Date: Friday, February 24, 2017 at 9:42 AM
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: Re: Read after Write inconsistent at times
WRT to NTP, I first encountered this issue on my first cluster. The problem
with ntp isn't just if you're
a.apache.org<mailto:user@cassandra.apache.org>"
<user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
Subject: Re: Read after Write inconsistent at times
WRT to NTP, I first encountered this issue on my first cluster. The problem
with ntp isn't just if you're doin
WRT to NTP, I first encountered this issue on my first cluster. The
problem with ntp isn't just if you're doing inserts, it's if you're doing
inserts in combination with deletes, and using server timestamps with a
greater variance than the period between the delete and the insert.
Basically, you
Hi,
Check the tombstone count, If is it to high, your query will be impacted.
If tombstone is a problem, you can try to reduce your "gc_grace_seconds" to
reduce tombstone count(Carefully because you use cross data centers).
Tchau,
Petrus Silva
On Fri, Feb 24, 2017 at 12:07 AM, Jan Kesten
Hi,
are your nodes at high load? Are there any dropped messages (nodetool
tpstats) on any node?
Also have a look at your system clocks. C* needs them in thight sync -
via ntp for example. Side hint: if you use ntp use the same set of
upstreams on all of your nodes - ideal your own one.
Have you checked that NTP is correctly synched across all nodes in your
cluster?
On Fri, 24 Feb 2017 at 17:29 Charulata Sharma (charshar)
wrote:
>
> Hi All,
>
> In my application sometimes I cannot read data that just got inserted.
> This happens very intermittently. Both
Hi All,
In my application sometimes I cannot read data that just got inserted. This
happens very intermittently. Both write and read use LOCAL QUOROM.
We have a cluster of 12 nodes which spans across 2 Data Centers and a RF of 3.
Has anyone encountered this problem and if yes what steps have