Can you give us an example of the duplicate records that comes back? How reliable is it (i.e. is it every record, is it one record per read, etc)? By any chance is it just the `data` field that duplicates while the other fields change per row?
> I don’t see duplicates in cqlsh. I've never seen this, and I can't think of a failure mode which would cause it to happen. Not to say it's impossible, but Cassandra's standard read path involves collapsing duplicate or otherwise overlapping answers from multiple replicas; such a thing would be a pretty substantial deviation. Especially since you don't see the duplicates in cqlsh, I have a hunch this is an application bug. On Fri, Oct 2, 2015 at 4:58 PM Robert Wille <[email protected]> wrote: > When I run the query "SELECT image FROM roll WHERE roll = :roll“ against > this table > > CREATE TABLE roll ( > roll INT, > image BIGINT, > data VARCHAR static, > mid VARCHAR, > imp_st VARCHAR, > PRIMARY KEY ((roll), image) > ) WITH gc_grace_seconds = 3456000 AND compaction = { 'class' : > 'LeveledCompactionStrategy', 'sstable_size_in_mb' : 160 }; > > I often get duplicate records back. Seems like a very simple query to > botch. I’m running 2.0.16 with RF=3 and CL=QUORUM and Java client 2.0.10.1. > I don’t see duplicates in cqlsh. Any thoughts? > > Thanks > > Robert > >
