I'll second that - we had some weird inconsistent reads for a long time
that we finally tracked to a small number of clients with significant clock
skew. Make very sure all your client (not just C*) machines have
tightly-synced clocks.
On Fri, Oct 12, 2018 at 7:40 PM maitrayee shah
wrote:
> We
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:
> Did it still timeout?
>
> Sent from my iPhone
>
> On Oct 12, 2018, at 1:11 PM, Abdul Patel wrote:
>
> With limit 11 this is
We have seen inconsistent read if the clock on the nodes are not in sync.
Thank you
Sent from my iPhone
> On Oct 12, 2018, at 1:50 PM, Naik, Ninad wrote:
>
> Hello,
>
> We're seeing inconsistent data while doing reads on cassandra. Here are the
> details:
>
> It's is a wide column
Hello,
We're seeing inconsistent data while doing reads on cassandra. Here are the
details:
It's is a wide column table. The columns can be added my multiple machines, and
read by multiple machines. The time between writes and reads are in minutes,
but sometimes can be in seconds. Writes
Did it still timeout?
Sent from my iPhone
> On Oct 12, 2018, at 1:11 PM, Abdul Patel wrote:
>
> With limit 11 this is query..
> Select * from table where status=0 and tojen(user_id) >=token(126838) and
> token(user_id) <= token
>> On Friday, October 12, 2018, Abdul Patel wrote:
>> Let me
With limit 11 this is query..
Select * from table where status=0 and tojen(user_id) >=token(126838) and
token(user_id) <= token wrote:
> Let me try with limit 11 ..we have 18 node cluster ..no nodes down..
>
> On Friday, October 12, 2018, Nitan Kainth wrote:
>
>> Try query with partition key
Let me try with limit 11 ..we have 18 node cluster ..no nodes down..
On Friday, October 12, 2018, Nitan Kainth wrote:
> Try query with partition key selection in where clause. But time for limit
> 11 shouldn’t fail. Are all nodes up? Do you see any corruption in ay
> sstable?
>
> Sent from my
Try query with partition key selection in where clause. But time for limit 11
shouldn’t fail. Are all nodes up? Do you see any corruption in ay sstable?
Sent from my iPhone
> On Oct 12, 2018, at 11:40 AM, Abdul Patel wrote:
>
> Sean,
>
> here it is :
> CREATE TABLE Keyspave.tblname (
>
Sean,
here it is :
CREATE TABLE Keyspave.tblname (
user_id bigint,
session_id text,
application_guid text,
last_access_time timestamp,
login_time timestamp,
status int,
terminated_by text,
update_time timestamp,
PRIMARY KEY (user_id, session_id)
) WITH
Cpuld you elaborate cross partition query?
On Friday, October 12, 2018, Durity, Sean R
wrote:
> I suspect you are doing a cross-partition query, which will not scale well
> (as you can see). What is the schema for the table involved?
>
>
>
>
>
> Sean Durity
>
>
>
> *From:* Abdul Patel
>
11 matches
Mail list logo
