Well, if it's the primary key there should only ever be one result. Is this the partition key and you also have a clustering key?
On Tue, Feb 14, 2017 at 1:43 PM Josh England <j...@tgsmc.com> wrote: > Super simple: > select * from table WHERE primary_key='foo'; > > -JE > > > On Tue, Feb 14, 2017 at 1:38 PM, sfesc...@gmail.com <sfesc...@gmail.com> > wrote: > > What is your query? I've seen this once when using secondary indices as it > has to reach out to all nodes for the answer. If a node doesn't respond in > time those records seem to get dropped. > > On Tue, Feb 14, 2017 at 1:37 PM Josh England <j...@tgsmc.com> wrote: > > All client interactions are from python (python-driver 3.7.1) using > default consistency (LOCAL_ONE I think). Should I try repairing all nodes > to make sure all data is consistent? > > -JE > > > On Tue, Feb 14, 2017 at 1:32 PM, Oskar Kjellin <oskar.kjel...@gmail.com> > wrote: > > What consistency levels are you using for reads/writes? > > Sent from my iPhone > > > On 14 Feb 2017, at 22:27, Josh England <j...@tgsmc.com> wrote: > > > > I'm running Cassandra 3.9 on CentOS 6.7 in a 6-node cluster. I've got a > situation where the same query sometimes returns 2 records (correct), and > sometimes only returns 1 record (incorrect). I've ruled out the > application and the indexing since this is reproducible directly from a > cqlsh shell with a simple select statement. What is the best way to debug > what is happening here? > > > > -JE > > > > > >
