That's it. The clock on one of the nodes was way off. Thanks!!
--
regards,
Gudmundur Johannsson
On Wed, Mar 11, 2015 at 3:42 PM, Roland Etzenhammer <
r.etzenham...@t-online.de> wrote:
> Hi,
>
> I think that your clocks are not in sync. Do you have ntp on all your
> nodes up and running with low
Hi,
I think that your clocks are not in sync. Do you have ntp on all your
nodes up and running with low offset? If not, setup ntp as first
probable solution. Cassandra relies on accurate clocks on all cluster
nodes for it's (internal) timestamps.
Do you see any error while writing? Or just w
Hi Gudmundur, each write and overwrite has a timestamp associated with it (you
can see these timestamps using the WRITETIME function). This timestamp is
provided by the Cassandra server if you don't explicitly supply it yourself
(which, judging by your queries, you are not). If the timestamp o
What happens if you use "update where." rather than insert?
On Wed, Mar 11, 2015 at 7:58 PM, Guðmundur Örn Jóhannsson <
gudmundur@gmail.com> wrote:
> I have a 3 node cluster of Cassandra version 2.0.9. My keyspace
> replication factor is 3 and I'm querying with consistency level ALL.
>
>
I have a 3 node cluster of Cassandra version 2.0.9. My keyspace replication
factor is 3 and I'm querying with consistency level ALL.
Problem: When I do an insert to overwrite an old row, the old data still
appears in all select queries! This does not apply to all cases, just a
subset of the rows i
