Date: Wed, 6 May 2009 15:09:33 -0400 From: Bill Moran <wmoran@potentialtech.com> To: Martin Turgeon <freebsd@optiksecurite.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: Advices for a jailed MySQL server Message-ID: <20090506150933.d0ef0178.wmoran@potentialtech.com> In-Reply-To: <4A01DBCE.9070304@optiksecurite.com> References: <4A01DBCE.9070304@optiksecurite.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In response to Martin Turgeon <freebsd@optiksecurite.com>: > Hi everyone, > > I'm starting to build a new dedicated MySQL server. I will be using > FreeBSD 7.2-REL. My plan is to jail the latest version of MySQL 5.0 and > to put the MySQL data outside the jail. My objective is to be able to > update MySQL without down time. My objective would be to create another > up to date MySQL jail and when I'm ready to make the switch, just point > the new jail to the data outside the jail using something like a nullfs > mount. > > Is someone using something like this? > > Did someone have any advice about how to update a MySQL server without > down time? > > Did someone have any advice on how to tune a dedicated MySQL server > running FreeBSD 7.2 (Dual core Xeon, 4G RAM, mirror RAID on a PERC5 > controler 2x146G 15K)? > > Thanks everyone for sharing your precious knowledge :) I expect that what you're trying to do will work, however it's horrifically error-prone during the upgrade procedure (what if you forget to stop the first MySQL before you start the new one!) If you need to do anything zero-downtime, then you probably want to run multiple MySQL instances and use database replication to keep the data in sync. That way you just switch which DB is master, then upgrade the slave ... rinse/repeat. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090506150933.d0ef0178.wmoran>