Re: Inconsistent query results and node state

On Thu, Mar 31, 2016 at 11:53 AM, Jason Kania wrote: > > To me it just seems like the timestamp column value is sometimes not being > set somewhere in the pipeline and the result is the epoch 0 value. > I agree, especially since you can't directly query this row and that

Re: Inconsistent query results and node state

and the result is the epoch 0 value. Thoughts on how to proceed? Thanks, Jason From: Tyler Hobbs <ty...@datastax.com> To: user@cassandra.apache.org Sent: Wednesday, March 30, 2016 11:31 AM Subject: Re: Inconsistent query results and node

Re: Inconsistent query results and node state

Thanks for the response. All nodes are using NTP. Thanks, Jason From: Kai Wang <dep...@gmail.com> To: user@cassandra.apache.org; Jason Kania <jason.ka...@ymail.com> Sent: Wednesday, March 30, 2016 10:59 AM Subject: Re: Inconsistent query results and node state Do you ha

Re: Inconsistent query results and node state

> > org.apache.cassandra.service.DigestMismatchException: Mismatch for key > DecoratedKey(-4908797801227889951, 4a41534b414e) > (6a6c8ab013d7757e702af50cbdae045c vs 2ece61a01b2a640ac10509f4c49ae6fb) That key matches the row you mentioned, so it seems like all of the replicas should have

Re: Inconsistent query results and node state

Do you have NTP setup on all nodes? On Tue, Mar 29, 2016 at 11:48 PM, Jason Kania wrote: > We have encountered a query inconsistency problem wherein the following > query returns different results sporadically with invalid values for a > timestamp field looking like the