The plan has changed slightly. Without going into the gory details, the old proxy will be shut down, DNS is changed, final data gets synched, and the the old proxy chains to the new proxy.
An automated process the emails anyone submitting to the old proxy to update thier config.
2006-04-03 21:50 DB Migration a bust.
As it turns out, something else on the machine won't work with MySQL 5.0, so I'm regrouping.In other news, the time change introduced a few bugs. Well, I introduced them, the time change just made me fix them.
Also, some of the new stuff is using dbConnections managed by Tomcat, rather than the pool I was mantaining. Hopefully this cures some threading issues I was weeking.
Lastly, some of the new stuff is using aggregated data along with query caching, which will hopefuly prove snappier. I'll migrate the old stuff later. ---
2006-03-23 21:36 DB Migration in the works
Due to some limitations of 4.01 MySQL, I've set up 5.0 on a test box, and will start running the fileWatcher in parallel. Once I'm comfortable that is working, the proxy pages will query from there while I get the primary DB upgraded. Hopefully you won't even notice.---
2006-03-19 21:19 Intro This is where to look to see what's in the works.
The only thing of interest is a planned DB upgrade. Some of the pages take many queries to put together, so I need to upgrade to MySql 4.1 to allow subselects. Data will be replicated to another machine, and the servlets/gather code redirected. It should be transparent.