I'll try it the repair. Using quorum tends to lead to too many timeout problems though. :(
-JE On Tue, Feb 14, 2017 at 1:39 PM, Oskar Kjellin <oskar.kjel...@gmail.com> wrote: > Repair might help. But you will end up in this situation again unless you > read/write using quorum (may be local) > > Sent from my iPhone > > On 14 Feb 2017, at 22:37, 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 >> > >> > >
