Ditto. I would mysqldump 5.0, load it onto a 5.5 (or 5.6) box that you have as a slave of the 5.0 master. The load may uncover some issues. Testing reads may uncover issues. The replication stream will test the writes; it may uncover issues.
After being comfortable with that, build new slaves off the 5.5/5.6 box. Then cutover writes to that box. And jettison the 5.0 boxes. 5.5 -> 5.6 may have more changes/improvements that all of 5.0->5.1->5.5. (Or, at least, Oracle salesmen would like you to believe it.) There is clearly a lot new optimizations in 5.6. So should you go all the way to 5.6? Maybe. You need to do a lot of shakedown anyway. > -----Original Message----- > From: Mihail Manolov [mailto:mihail.mano...@liquidation.com] > Sent: Thursday, February 14, 2013 2:22 PM > To: Mike Franon > Cc: Akshay Suryavanshi; <mysql@lists.mysql.com> > Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6 > > You could jump from 5.0 directly to 5.5 and skip 5.1. I have without > any issues. There are some configuration file change, which you may > want to consider checking. I definitely recommend upgrading your > development servers for an extensive testing. Some queries _may_ run > slower or not work at all and you may have to rearrange how you join > tables in your queries. > > The upgrade from 5.5 to 5.6 should me smoother, though. > > > On Feb 14, 2013, at 4:28 PM, Mike Franon wrote: > > > Great thanks for the info, I guess the best way to do this is take a > > spare server, set it up with our standard setup, and then start the > > upgrade as you said 5.0 -> 5.1 -> 5.5, test and then upgrade to 5.6 > > and test. > > > > > > > > > > > > > > > > > > On Thu, Feb 14, 2013 at 4:22 PM, Akshay Suryavanshi > > <akshay.suryavansh...@gmail.com> wrote: > >> Mike, > >> > >> 5.6 is GA now, so its stable release. Also you should not jump to > 5.6 > >> directly, atleast from 5.0. > >> > >> There are many bug fixes and changes in 5.1, so you should consider > >> this way. > >> > >> 5.0-->5.1-->5.5 (all slaves first, and then the master) > >> > >> And further 5.5 --> 5.6 (again all slaves first and then the master) > >> > >> Hope this helps. > >> > >> Cheers! > >> > >> On Fri, Feb 15, 2013 at 2:38 AM, Mike Franon <kongfra...@gmail.com> > wrote: > >>> > >>> I have 1 master with many slaves, using the master only for inserts > >>> and the rest are readers. > >>> > >>> > >>> Is 5.6 stable? Or better off to go to 5.5? > >>> > >>> If so do I need to make a few steps or can go straight from 5.0 to > 5.6? > >>> > >>> > >>> Any best practices and recommendations? > >>> > >>> Thanks > >>> > >>> -- > >>> MySQL General Mailing List > >>> For list archives: http://lists.mysql.com/mysql > >>> To unsubscribe: http://lists.mysql.com/mysql > >>> > >> > > > > -- > > MySQL General Mailing List > > For list archives: http://lists.mysql.com/mysql > > To unsubscribe: http://lists.mysql.com/mysql > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
