cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ahmad Emneina <aemne...@gmail.com>
Subject Re: What are the exact steps when a database failure occurs in the presence of MySQL replication?
Date Wed, 29 May 2013 19:09:24 GMT
This is the page you'll want to take a look at:
https://dev.mysql.com/doc/refman/5.1/en/replication-solutions-switch.html


On Wed, May 29, 2013 at 2:56 AM, Ryan Lei <ryanlei750328@gmail.com> wrote:

> I was following the unpublished CS 4.1 Installation Guide to test MySQL
> replication:
>
> http://jenkins.cloudstack.org/job/docs-4.1-installguide/lastSuccessfulBuild/artifact/Apache_CloudStack-4.1.0-Installation_Guide-en-US.pdf
>
> I have completed all the steps in "Sec. 9.3. Database Replication", and
> suppose I can verify that all replication works by manually querying the
> slave database.
>
> In "Sec. 9.3.1. Failover," it says:
>
> This will provide for a replicated database that can be used to implement
> manual failover for the Management Servers. CloudStack failover from one
> MySQL instance to another is performed by the administrator. In the event
> of a database failure you should:
>
> 1. Stop the Management Servers (via service cloudstack-management stop).
> 2. Change the replica's configuration to be a master and restart it.
> 3. Ensure that the replica's port 3306 is open to the Management Servers.
> 4. Make a change so that the Management Server uses the new database. The
> simplest process
> here is to put the IP address of the new database server into each
> Management Server's /etc/
> cloud/management/db.properties.
> 5. Restart the Management Servers
>
> What are the exact commands to perform in step 2?
>
> http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-replication-failover.html
> I'm very new to MySQL replication and clustering things, not sure if any
> part of this page is what I want. Plase help. (checkpoint? NDB? )
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message