This is probably worth talking about now, since we are working
on the mysql module for the next several weeks. Using Matt's
read/update patch as a starting point the mysql functions
are broken up into read-only queries and update queries
with separate definitions in vmysql.h for two mysql login
connections. One for updates and one for read only.
I don't have any clean ideas yet on how to handle the
three cases most people are running into:
1) one mysql server for everything
2) replicated mysql system, with one read only server (slave)
and one update server (master)
3) a primary server and a backup server
Anyone have any ideas?
Ken Jones
Mark Lane writes:
> Is the data static? If not it is probably not worth the effort as you would
> have to send every write to every mysql server. If it is static then sure
> just tell the program calling mysql to open another mysql server if the
> first one fails
>
> for example something like this.
>
> if (!(connection = mysql_connect (host, user, password))) then
> connection=mysql_connection (host2, user, password);
>
> Of Course this will require rewriting the mysql login section of vchkpw.
>
> Mark
>
> ----- Original Message -----
> From: "Jeffrey Iskandar Ahmad" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, May 29, 2001 7:26 PM
> Subject: mysql high availability
>
>
> Hi guys,
> Is there a feature to enable failover if primary mysql does not respond and
> go to secondary mysql server. Is there anyway to enable multiple point of
> failure in any kind of setup?.
>
> Thanks
>
> Regards,
> Jeffrey Iskandar Ahmad
> System Engineer
> Technology Division
> Time dotNet bhd
>
>
>
