Okay, just thought I’d throw it out there. I just so happened to miss that
little tidbit from the upgrade guide and got bit by it.
That is an odd problem, then. I hope you find your answer. Please update
us if you figure it out. Very curious to hear the answer.
On Sat, Oct 13, 2018 at 4:09
Thanks James. Yeah, we're using the datastax java driver. But we're on version
2.1.10.2. And we are not using the client side timestamps.
From: James Carman
Sent: Saturday, October 13, 2018 12:55:51 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra:
Thanks Elliot. We've verified that the cassandra node clocks are in sync. And
we're not using client side timestamps, so client machine clocks wouldn't
matter ?
From: Elliott Sims
Sent: Friday, October 12, 2018 10:16:58 PM
To: user@cassandra.apache.org
Subject:
Are you using the Java driver? The default timestamp generator is
client-side now (since 3.0 I believe), so if you don’t change it, you need
your client clocks to be in sync also.
On Sat, Oct 13, 2018 at 1:24 PM Naik, Ninad wrote:
> Thanks Maitrayee. I should have mentioned this as one of the
Thanks Maitrayee. I should have mentioned this as one of the things we
verified. The clocks on cassandra nodes are in sync.
From: maitrayee shah
Sent: Friday, October 12, 2018 6:40:25 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra: Inconsistent data on
Using partition key is best way to query
Sent from my iPhone
> On Oct 12, 2018, at 6:49 PM, Abdul Patel wrote:
>
> Yes with range queries its timing out, one question was the where condition
> is primary key rather than clustering key.
>
>> On Friday, October 12, 2018, Nitan Kainth wrote:
Thanks Ben for the detailed insight. Btw we are planning to set up
Kubernetes Cassandra cluster in Development. We wanted to know what are the
possible problems we face if we go by Kubernetes
On Thu, Oct 11, 2018 at 4:06 PM Ben Bromhead wrote:
> This is a fairly high-level question which could
