I agree with Jeff here: It's not recommended to do that but it should be still fine :).
Something that might be slightly safer (even though 3.11.0 is buggy as mentioned above...) could be to add a 3.11.0 cluster. Do the streaming with 3.11.0, upgrade the new DC only, switch clients over, terminate old DC. Here I talked about it a bit: https://thelastpickle.com/blog/2019/02/26/data-center-switch.html#use-cases. There are also other information you might find useful, as this post is a runbook that details actions to do a Data Center switch. It looks like a good fit :). C*heers, ----------------------- Alain Rodriguez - al...@thelastpickle.com France / Spain The Last Pickle - Apache Cassandra Consulting http://www.thelastpickle.com Le lun. 1 juil. 2019 à 21:38, Rahul Reddy <rahulreddy1...@gmail.com> a écrit : > Thanks Jeff, > > We want to migrate to Apache 3.11.3 once entire cluster in apache we > eventually decommission datastax DC > > On Mon, Jul 1, 2019, 9:31 AM Jeff Jirsa <jji...@gmail.com> wrote: > >> Should be fine, but you probably want to upgrade anyway, there were a few >> really important bugs fixed since 3.11.0 >> >> > On Jul 1, 2019, at 3:25 AM, Rahul Reddy <rahulreddy1...@gmail.com> >> wrote: >> > >> > Hello All, >> > >> > We have datastax Cassandra cluster which uses 3.11.0 and we want to add >> new DC with apache Cassandra 3.11.3. we tried doing the same and data got >> streamed to new DC. Since we are able to stream data any other issues we >> need to consider. Is it because of same type of sstables used in both the >> cases it let me add new DC? >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org >> For additional commands, e-mail: user-h...@cassandra.apache.org >> >>
