Hi all ,
I recived few positive messages form the list ,
so I decided to make a public port of the whole thing .

Why it could be used ?
Before you start playing with all this game , you have to understand the
limitations
of my implementation .
All this only allow you to have a sort of sql cluster for an web cluster for
example
where you can loose a server without any down time in your web cluster.
So it give you all time you need to repair the broken server and bring it
back on line .

It does not provide any failover to the web part for that I recommend if you
have few bucks to by an  alteon or foundry loadbalancer , and it will do
this kind of job very well , if you dont have any bucks go to the LVS . (i
can help with exact alteon or foundry configurations)

I'll build a step by step guide on what you need :
1) Dynamic Dns conf .
all bind conf , and dyn updates
2) Mysql replication conf
there is a lot of docs around  :=)
3) Watch dog and failover update scripts
I'll clean my code to make it more frindly for evry body .
4) Wrappers .
Yes to use this kind of cluster you need a wrapper that will separate select
querys and send them to the slave .
I have wrappers in :
Perl ( mod_perl friendly version ) (using apache::dbi)
Java . Php .
C/C++ (not finished yet )
5) Set of scripts witch you should use to resync a server after a crash .

With all this it should be good for you to wait for mysql team to release
all
this in a real cluster . (like sun && oracle)

I'll do all this as soon as possible .

Very best
Constantin Bogomolnyi

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "Bogomolnyi Constantin" <[EMAIL PROTECTED]>
Sent: Friday, March 16, 2001 1:50 PM
Subject: Re: Failover and Replication [HOWTO]


> Hi Bogomolnyi,
>
> I would be interested in your scripts.  I have been watching this
conversation with interest.  I have an application for exactly the same
thing.  I am going to have 3
> mysql servers, which I would like to use as master and slaves.  I also
would like to know if it would work with web servers also?
>
> Edward
>
> 3/15/2001 12:14:21 AM, "Bogomolnyi Constantin" <[EMAIL PROTECTED]>
wrote:
>
> >Hi ,
> >I posted a few considerations about fialover implementation , to the list
,
> >but i don't recived any feed back , well lets see what we have :
> >
> >But i write a bunch of perl scripts and now I use them in production and
> >very happy with the result .
> >Here what I have :
> >Baiscly what I want is an sql cluster (composed of min 2 servers )
> >that can survive a crash and still working . (we all want this )
> >
> >so i set up a very simple replication between a master and a slave
> >and I use an dynamic dns to locate slave && master .
> >like this :
> >master.sql.corp.com        192.168.1.100
> >slave1.sql.corp.com          192.168.1.101
> >slaveN.sql.corp.com          192.168.1.10N
> >
> >I have a wrapper that send all selects to the slaves and updates to the
> >master
> >i have an advanced watchdog that check if all sqls are up , and if :
> >SLAVE FAIL :
> >    I simply updater the DNS to slave-1 and all applications still
working
> >    the dns update is very quick (1sec) .
> >MASTER FAIL :
> >    I simply update the DNS to the NEXT slave  for the master and next
slave
> >for
> >    the slave (to avoid all selects on the master)
> >    I run change master to on all slaves , and the party keep going
> >
> >this works from 2 to N servers ,
> >
> >I can setup an opensource project , and put all watchdog/dns update
/setup
> >stuff
> >in it if any body is intrestead in this .
> >
> >I run this for 2 month and all goes very very well i'm very happy with
this
> >.
> >
> >My cluster is :
> >5 pc , and I use it for a web cluster (10 pc) so I use 1 slave for 2
httpds
> >.
> >
> >For the moment after an server fail , i sync it back using a simple
script ,
> >the watch dog don't do it because i dont want a buggy server coming in
and
> >out
> >the party .
> >
> >I would be very happy to release all implementation .
> >
> >Very best
> >
> >Constantin Bogomolnyi
> >
> >
> >----- Original Message -----
> >From: "Bryan Coon" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Sent: Wednesday, March 14, 2001 6:10 PM
> >Subject: Failover and Replication
> >
> >
> >> Hi,
> >>
> >> We are implementing a linux cluster, and rather than get gouged by
oracle
> >> (in performance and licensing) would muuuuuch rather use MySQL.  I
> >searched
> >> through the archives and found several references to failover and
> >> replication but still have some questions.
> >>
> >> If I understand correctly, replication creates a working copy of mysql
on
> >> another server, but it looks like the algorithm to automatically change
> >> slave to master if the master dies will not be added until mysql 4.x
(from
> >> 11.4 in the manual).
> >>
> >> Is this still the case?  Im not sure when that was written, perhaps
there
> >is
> >> news on this front?  I also did not find a expected release date
> >>
> >> Does anyone have any stories/suggestions/experiences in regards to
rolling
> >> our own monitoring script?
> >>
> >> Thanks!
> >> Bryan
> >>
> >> ---------------------------------------------------------------------
> >> Before posting, please check:
> >>    http://www.mysql.com/manual.php   (the manual)
> >>    http://lists.mysql.com/           (the list archive)
> >>
> >> To request this thread, e-mail <[EMAIL PROTECTED]>
> >> To unsubscribe, e-mail
> ><[EMAIL PROTECTED]>
> >> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
> >>
> >>
> >
> >
> >---------------------------------------------------------------------
> >Before posting, please check:
> >   http://www.mysql.com/manual.php   (the manual)
> >   http://lists.mysql.com/           (the list archive)
> >
> >To request this thread, e-mail <[EMAIL PROTECTED]>
> >To unsubscribe, e-mail
<[EMAIL PROTECTED]>
> >Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
> >
> >
> >
>
>
>


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to