[Pacemaker] Circular replication help needed - how to make sure VIP runs on same node with a healthy mysql

[Florian Haas]

On 2011-11-05 18:20, Attila Megyeri wrote:
> Hello,
> 
>  
> 
> I am having a hard time configuring a relatively simple mysql environment.
> 
>  
> 
> What I’d like to achieve is:
> 
> ·         One master and a slave, with replication
> 
> ·         Relatively quick failover if the master node, or Mysql fail.
> 
>  
> 
> I tried the Mysql cluster approach, but seemed to be too slow, and to
> many limitations (foreign keys, triggers, views, etc).
> 
>  
> 
> I decided to go with the Mysql replication.

You want a simple 2-node MySQL cluster with failover? Why not go with
DRBD then, as everyone else would in that situation?

> Tried to use the mysql RA from clusterlabs 3.9.2 – but no luck,
> replicaiton simply did not work out.

Sorry to say this, but as a co-author of that agent I'll say that that's
exactly the kind of feedback we strongly dislike, as it doesn't help us
at all improving the agent, or its documentation. So,

- What were you trying to achieve?
- What was your configuration?
- What went wrong?
- What were you unable to fix?

For the DRBD based approach (which I would highly recommend), do
consider taking a look at
http://www.hastexo.com/content/mysql-high-availability-sprint-launch-pacemaker.
We'll be happy to provide you with the virtual images used in this
tutorial, so you can set things up yourself in a cleanroom testing
environment.

Cheers,
Florian

-- 
Need help with High Availability?
http://www.hastexo.com/now