Thanks for reporting back, Tom. Can you drop a comment on the ticket with a sentence or two describing your specific case and that speculative_retry = NONE was a valid work-around?
That will make it easier for the next folks that come along to have a concrete problem/solution in a single comment on that ticket. Glad to hear it worked, though. On Tue, Sep 8, 2015 at 3:38 PM, Tom van den Berge <tom.vandenbe...@gmail.com > wrote: > Nate, > > I've disabled it, and it's been running for about an hour now without > problems, while before, the problem occurred roughly every few minutes. I > guess it's safe to say that this proves that CASSANDRA-9753 > <https://issues.apache.org/jira/browse/CASSANDRA-9753> is the cause of > the problem. > > I'm very happy to finally know the cause of this problem! Thanks for > pointing me in the right direction. > Tom > > On Tue, Sep 8, 2015 at 9:13 PM, Nate McCall <n...@thelastpickle.com> > wrote: > >> Just to be sure: can this bug result in a 0-row result while it should be >>> > 0 ? >>> >> Per Tyler's reference to CASSANDRA-9753 >> <https://issues.apache.org/jira/browse/CASSANDRA-9753>, you would see >> this if the read was routed by speculative retry to the nodes that were not >> yet finished being built. >> >> Does this work as anticipated when you set speculative_retry to NONE? >> >> >> >> >> -- >> ----------------- >> Nate McCall >> Austin, TX >> @zznate >> >> Co-Founder & Sr. Technical Consultant >> Apache Cassandra Consulting >> http://www.thelastpickle.com >> > > -- ----------------- Nate McCall Austin, TX @zznate Co-Founder & Sr. Technical Consultant Apache Cassandra Consulting http://www.thelastpickle.com
