|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
204.94.81.82
It's time.
To complete the final move to the new servers, I'll need to take down the site for about 2 1/2 to 3 hours. In addition to syncing all the data from one server to another, I also need to dump and load the db which takes most of the time to deal with some issues with a newer version of MySQL.
I was hoping to do this in just a half hour, but upgrading the db just takes a while to load 8 million posts and it became clear that it was best to just do it and get it done now.
Once we're done and sure that everything is running as it should, then we'll have one more disruption the following week or next to actually move the new servers to a new data center. It's taken us nearly 5 months to complete this upgrade and I'm quite happy with the performance improvement. If you've used the Search app lately, you're seeing the new servers in action with a dedicated search db server. Using Solid State Drives has delivered a huge boost in performance.
Wish me well.
Thanks for the support.
-Rod
Follow Ups:
Maybe you could set up the new version of the DB software, make a copy of the database, hose over the 8 million posts from the copy (so the live db is still functional), verify that it works, put the new server online, and then update the database with whatever new posts were made since the time you made the db copy.Essentially, what I'm saying is to do as much prep offline as possible, so that downtime is minimized. I'm pretty sure that MySQL has a way to update a database with the changes which were made after the last backup copy, a process which is often known as "batch processing", "batch updaing" or "syncronizing". It'd be too bad if you have to take down the site for three hours, bring up the new version, and discover that something is wrong and it'll be two more days before it works.
Having said that, whenever I release a new version of my db app, I tell clients to go offline during the update.
Good luck!
:)
Edits: 02/26/15 02/26/15
Yeah, if it was only the db, perhaps, but I need to convert the character sets which can only be done by dropping the db and the creating it and loading the data. I've tried every other option. Since the two versions are incompatible, a db slave won't update with the data from the old db. I tried that too.
In addition, I have to sync the new server with all the cached html files and new image uploads which takes a while too. There's just no good way to have people posting and getting stuff updated in 2 places.
-Rod
I love Audio Asylum!
...This is a convenient and acceptable time for me, Rod. I just thought you’d like to know.
Keep up the good work.
This site is saving the health care system millions!
Oh, good luck with your tinkering.
Smile
Sox
:-)!
Warmest
Tim Bailey
Skeptical Measurer & Audio Scrounger
Excellent timing. I have a dental appointment Thursday morning.
:)
Go for It! Rod-
Post a Followup:
FAQ |
Post a Message! |
Forgot Password? |
|
||||||||||||||
|
This post is made possible by the generous support of people like you and our sponsors: