Comments on: Redundant MySQL set-up for Amazon EC2 http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/ Cloud Computing. Delivered. Thu, 18 Mar 2010 18:16:54 +0000 http://wordpress.com/ hourly 1 By: Thorsten http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-536 Thorsten Mon, 03 Nov 2008 05:39:15 +0000 http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-536 Nitin: with EBS you still want a redundant set-up, it's by far the fastest way to switch to a fresh instance if the current one has a problem. Also, if something bad happens within the availability zone, you may not be able to get to your volume... Better have a slave running in a 2nd zone! Nitin: with EBS you still want a redundant set-up, it’s by far the fastest way to switch to a fresh instance if the current one has a problem. Also, if something bad happens within the availability zone, you may not be able to get to your volume… Better have a slave running in a 2nd zone!

]]> By: Nitin http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-513 Nitin Mon, 27 Oct 2008 18:52:48 +0000 http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-513 Is that still necessary with persistent block storage? Is that still necessary with persistent block storage?

]]> By: Dare Obasanjo aka Carnage4Life - Some Thoughts on Amazon's Elastic Block Store http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-385 Dare Obasanjo aka Carnage4Life - Some Thoughts on Amazon's Elastic Block Store Thu, 21 Aug 2008 13:03:02 +0000 http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-385 [...] a persistent filesystem, developers on Amazon's cloud computing platform have had to come up with sophisticated solutions involving backing data up manually from EC2 to S3 to get the desired [...] [...] a persistent filesystem, developers on Amazon’s cloud computing platform have had to come up with sophisticated solutions involving backing data up manually from EC2 to S3 to get the desired [...]

]]> By: Thorsten http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-367 Thorsten Wed, 20 Aug 2008 22:35:53 +0000 http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-367 It is definitely possible, but not something we provide out of the box. All the scripts for the replication are open and modifiable by our customers, so you'd have a good starting point. Some of the details are that we do an LVM snapshot followed by a copy of the files to initialize the slave. Unless you use distinct data files all InnoDB tables end up in one file and would get copied to all slaves. If that's acceptable, all you'd have to do is modify the set-up of each slave to only keep replicating the appropriate tables. If you want to avoid the initial replication of all the data then more work is required. Hope this helps. It is definitely possible, but not something we provide out of the box. All the scripts for the replication are open and modifiable by our customers, so you’d have a good starting point. Some of the details are that we do an LVM snapshot followed by a copy of the files to initialize the slave. Unless you use distinct data files all InnoDB tables end up in one file and would get copied to all slaves. If that’s acceptable, all you’d have to do is modify the set-up of each slave to only keep replicating the appropriate tables. If you want to avoid the initial replication of all the data then more work is required. Hope this helps.

]]> By: Marcello http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-360 Marcello Thu, 14 Aug 2008 10:23:10 +0000 http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-360 Hi all, Is it possible using rightscale's interface to implement, at the same time, a redundant MySQL Set-up and a replication of many slaves containing only a subset of the tables present in the master? Architecture: 1 master, 1 or + slave(s) replicated with all tables for redundant purpose 1 or + slave(s) replicated with a subset of the tables for performance purpose As you can guess, the application will be a 90%read-10%write. I think it may be possible using 3 different AMI and add/start/stop. Regards, Marcello Hi all,
Is it possible using rightscale’s interface to implement, at the same time, a redundant MySQL Set-up and a replication of many slaves containing only a subset of the tables present in the master?

Architecture:
1 master,
1 or + slave(s) replicated with all tables for redundant purpose
1 or + slave(s) replicated with a subset of the tables for performance purpose

As you can guess, the application will be a 90%read-10%write.

I think it may be possible using 3 different AMI and add/start/stop.

Regards,
Marcello

]]> By: Thorsten http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-300 Thorsten Tue, 08 Jul 2008 00:19:38 +0000 http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-300 David, good question. First of all, reboots are actually very rare. I suspect they have more to do with transient hardware failures (like double memory ECC errors) than AWS doing. We currently don't automatically promote the slave to master as this is a very delicate operation. Gotta ensure the master is really not servicing requests first, etc. David, good question. First of all, reboots are actually very rare. I suspect they have more to do with transient hardware failures (like double memory ECC errors) than AWS doing. We currently don’t automatically promote the slave to master as this is a very delicate operation. Gotta ensure the master is really not servicing requests first, etc.

]]> By: David http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-277 David Sat, 14 Jun 2008 14:40:46 +0000 http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-277 Hi there. There is good insight given in the article. Question I have has to to with rebooting. At any moment you can loose an instance which is fine. But Amazon, for maintenance may reboot the machine without you knowing exactly when this will happen. You may also want to reboot for server updates (though this would be scheduled). Let's say Amazon admins reboot or for some reason it reboots itself, I assume the slave detects the loss of master and will take over and potential initiate launch of a new slave. Can you explain what you are doing for a reboot situation when you don't want folks on the other end of your data seeing the app is dead. Obviously the original master will be coming back up also. Hi there. There is good insight given in the article. Question I have has to to with rebooting. At any moment you can loose an instance which is fine. But Amazon, for maintenance may reboot the machine without you knowing exactly when this will happen. You may also want to reboot for server updates (though this would be scheduled). Let’s say Amazon admins reboot or for some reason it reboots itself, I assume the slave detects the loss of master and will take over and potential initiate launch of a new slave. Can you explain what you are doing for a reboot situation when you don’t want folks on the other end of your data seeing the app is dead. Obviously the original master will be coming back up also.

]]> By: links for 2008-06-03 « PaxoBlog http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-270 links for 2008-06-03 « PaxoBlog Tue, 03 Jun 2008 23:30:28 +0000 http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-270 [...] Redundant MySQL set-up for Amazon EC2 « RightScale Blog What we’ve built is a mysql master/slave set-up with backup to Amazon S3. The set-up consists of one mysql master server which is the primary database server used by the application. We assume it runs on its own EC2 instance but it could probably share (tags: mysql replication s3 rightscale) [...] [...] Redundant MySQL set-up for Amazon EC2 « RightScale Blog What we’ve built is a mysql master/slave set-up with backup to Amazon S3. The set-up consists of one mysql master server which is the primary database server used by the application. We assume it runs on its own EC2 instance but it could probably share (tags: mysql replication s3 rightscale) [...]

]]> By: example master/slave on Ec2/S3 « Hefta-Gaub Development Blog http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-98 example master/slave on Ec2/S3 « Hefta-Gaub Development Blog Thu, 10 Apr 2008 21:19:00 +0000 http://blog.rightscale.com/2007/08/20/redundant-mysql-set-up-for-amazon-ec2/#comment-98 [...] Redundant MySQL set-up for Amazon EC2 What we’ve built is a mysql master/slave set-up with backup to Amazon S3. The set-up consists of one mysql master server which is the primary database server used by the application. We assume it runs on its own EC2 instance but it could probably share the instance with the application. We install LVM (linux volume manager) on the /mnt partition and place the database files there. We use LVM snapshots to back up the database to S3, this means that we get a consistent backup of the database files with only a sub-second hiccup to the database. [...] [...] Redundant MySQL set-up for Amazon EC2 What we’ve built is a mysql master/slave set-up with backup to Amazon S3. The set-up consists of one mysql master server which is the primary database server used by the application. We assume it runs on its own EC2 instance but it could probably share the instance with the application. We install LVM (linux volume manager) on the /mnt partition and place the database files there. We use LVM snapshots to back up the database to S3, this means that we get a consistent backup of the database files with only a sub-second hiccup to the database. [...]

]]>