Subject: Re: Cassandra: Inconsistent data on reads (LOCAL_QUORUM)
[ This email has been sent from a source external to Epsilon. Please use
caution when clicking links or opening attachments. ]
Ninad,
> Here's a bit more information:
>
> -Few rows in this column family can grow quite wid
elp !
From: Mick Semb Wever
Sent: Wednesday, October 24, 2018 4:12:57 AM
To: user@cassandra.apache.org
Subject: Re: Cassandra: Inconsistent data on reads (LOCAL_QUORUM)
[ This email has been sent from a source external to Epsilon. Please use
caution when clicking links or opening attachments. ]
Ni
Ninad,
> Here's a bit more information:
>
> -Few rows in this column family can grow quite wide (> 100K columns)
>
> -But we keep seeing this behavior most frequently with rows with just 1 or
> two columns . The typical behavior is: Machine A adds a new row and a column.
> 30-60 seconds later
dra: Inconsistent data on reads (LOCAL_QUORUM)
[ This email has been sent from a source external to Epsilon. Please use
caution when clicking links or opening attachments. ]
> 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 cl
> 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.
Just to check Ninad. If you are using Cassandra-2.1 (native protocol
v3) and the java driver version 3.0 or above, then you would be using
client-side
Yup. Verified again that this table is being written, read, and replicated to
just one data center.
From: Naik, Ninad
Sent: Monday, October 15, 2018 1:18:43 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra: Inconsistent data on reads (LOCAL_QUORUM)
Let
Let me double check that.
From: Jeff Jirsa
Sent: Monday, October 15, 2018 11:49:10 AM
To: user@cassandra.apache.org
Subject: Re: Cassandra: Inconsistent data on reads (LOCAL_QUORUM)
[ This email has been sent from a source external to Epsilon. Please use
7 PM
> To: user@cassandra.apache.org
> Subject: Re: Cassandra: Inconsistent data on reads (LOCAL_QUORUM)
>
> [ This email has been sent from a source external to Epsilon. Please use
> caution when clicking links or opening attachments. ]
>
> If this is 2.1 AND you do de
Thanks Jeff. We're not doing deletes, but I will take a look at this jira.
From: Jeff Jirsa
Sent: Sunday, October 14, 2018 12:55:17 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra: Inconsistent data on reads (LOCAL_QUORUM)
[ This email has been sent
@cassandra.apache.org
> Subject: Re: Cassandra: Inconsistent data on reads (LOCAL_QUORUM)
>
> [ This email has been sent from a source external to Epsilon. Please use
> caution when clicking links or opening attachments. ]
>
> We have seen inconsistent read if the clock on the no
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: Cassandra: Inconsistent data on reads (LOCAL_QUORUM)
>
>
> [ This email has been sent from a source external to Epsilon. Please use
> caution when clicking links or opening attachments. ]
> Are you using the Java driver? The default t
_
From: maitrayee shah
Sent: Friday, October 12, 2018 6:40:25 PM
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Cassandra: Inconsistent data on reads (LOCAL_QUORUM)
[ This email has been sent from a source external to Epsilon. Please use
caution when cl
: Re: Cassandra: Inconsistent data on reads (LOCAL_QUORUM)
[ This email has been sent from a source external to Epsilon. Please use
caution when clicking links or opening attachments. ]
I'll second that - we had some weird inconsistent reads for a long time that we
finally tracked to a small
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 reads (LOCAL_QUORUM)
>
&
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
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
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
17 matches
Mail list logo
