On Wed, Sep 9, 2015 at 1:05 AM, Tom van den Berge <tom.vandenbe...@gmail.com > wrote:
> >> I've learned from experience that the node immediately joins the cluster, >>> and starts accepting reads (from other DCs) for the range it owns. >> >> >> This seems to be the incorrect assumption at the heart of the confusion. >> You "should" be able to prevent this behavior entirely via correct use of >> ConsistencyLevel and client configuration. >> > > That is correct, but I just learned that CASSANDRA-9753 > <https://issues.apache.org/jira/browse/CASSANDRA-9753> is (in my > situation) causing problems by incorrectly sending reads to the new DC. A > work around for this bug is to set speculative_retry to 'NONE' for all > involved tables. This seems to solve the issue for me. > Ok, phew, "glad" it is "just" CASSANDRA-9753 <https://issues.apache.org/jira/browse/CASSANDRA-9753>. :D =Rob
