What's your keyspace replication strategy? On Thu, Sep 3, 2015 at 3:16 PM Tom van den Berge <tom.vandenbe...@gmail.com> wrote:
> Thanks for your help so far! > > I have some problems trying to understand the jira mentioned by Rob :( > > I'm currently trying to set up the first node in the new DC with > auto_bootstrap = true. The node then becomes visible with status "joining", > which (hopefully) prevents other DCs from sending queries to it. > > Do you think this will work? > > > > On Thu, Sep 3, 2015 at 9:46 PM, Robert Coli <rc...@eventbrite.com> wrote: > >> On Thu, Sep 3, 2015 at 12:25 PM, Bryan Cheng <br...@blockcypher.com> >> wrote: >> >>> I'd recommend you enable tracing and do a few queries in a controlled >>> environment to verify that queries are being routed to your new nodes. >>> Provided you have followed the procedure outlined above (specifically, have >>> set auto_bootstrap to false in your new cluster), rebuild has not been run, >>> the application is not connecting to the new cluster, and all your queries >>> are run at LOCAL_* quorum levels, I do not believe those queries should be >>> routed to the new dc. >>> >> >> Other than CASSANDRA-9753, this is true. >> >> https://issues.apache.org/jira/browse/CASSANDRA-9753 (Unresolved; ): >> "LOCAL_QUORUM reads can block cross-DC if there is a digest mismatch" >> >> =Rob >> >> > -- Regards, Ryan Svihla
