Just in case anyone else lands here, Mongo doesn't support mixed mode replica set with 2.6.x and 3.2.x -- I learned that the hard way, adding a new 3.2 member to the replica set to work on upgrading the nodes.
I had to remove that node, and build all new 3.0 nodes; now I'm in the process of moving the 3.0 nodes to 3.4.1 On Thursday, December 17, 2015 at 11:52:48 AM UTC-5, Darko Luketic wrote: > > Would you recommend staying on 3.0 or is it safe to upgrade to 3.2 in a > single mongos cluster with 3 rs? > aka "is it safe to upgrade to 3.2"? > > "There are still a couple of upstream issues" sounds like "sit it out" > > On Monday, December 7, 2015 at 3:38:00 AM UTC+1, Gustavo Niemeyer wrote: >> >> ... >> - Several tweaks in the test suite to make MongoDB 3.2 happy. There are >> still a couple of upstream issues that need handling before this is fully >> sorted. >> ... >> gustavo @ http://niemeyer.net >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
