Re: Replication

[Juergen H]

hello maxim,
i have serach (and try to find myself) a better way to reduct the handling on failover. ich any server crash a simple loadbalancer can handle the switch off of this server.
and the other... if any fails other works without the failing server.
and redudance on proxy-side? yes we have!

let me show the hole config of 4 servers with proxy-install-place:

(A --> proxy) --> B,C,D
(B --> proxy) --> A,C,D
(C --> proxy) --> A,B,D
(D --> proxy) --> A,B,C

(A --> proxy) --> B,C,D means
one server with mysql. the applikation runs on Server A and connect only to serer
A local. Server A have installed the Proxy. The bundle applikation, mysql and proxy are on one pfysikal server. if any fails the server is switching off. Server A,B,C,D applikation are connectet over loadbalancer to front-network.
if i want add one server i stop one server, copy this complete content, give new ip's and change the config to get replication from 'E'. starting the stopd server and the new one.

the traffic for writes are the same as for circluar replication. for circluar replication server A sends writes to B this sends to C this sends D and this to A. A know about this is my write and drop it for sending to B. if on same time B make writes it send like A in the circle . so every server have to write from all other servers.

yes... i know ...
the right config are:

A -->|
B -->| (Proxy D)
C -->|

because mysql can only have one master. the bundle on one server must know where to get replication-information.

the ID-Problem is the same for circluar replication... if i write to server A and request server C for this ID it fails if replication is to slow (ore blocked if locking). the loadbalacer must bind one client to fix server (and this realy works). so on applikation-side no changes have to made. ore you mean replication-ID (master-replication-position)?