Sorry, I said it bad.
If I have opened connection with mysql-proxy and mysql-server crashes
then mysql-proxy doesnt detect it and still sends queries to crashed
server. I mean it would connect to running server and send query there.
So this is unusable for applications that have opened connections for a
long time.
Norbert Tretkowski napsal(a):
tags 513558 +unreproducible
thanks
Am Freitag, den 30.01.2009, 07:14 +0100 schrieb Vladimir Rajnys:
My /etc/default/mysql-proxy:
ENABLED="true"
OPTIONS="--proxy-address=127.0.0.5:3306 --proxy-backend-addresses=127.0.0.1:3306
--proxy-backend-addresses=10.0.0.5:3306"
If I stop mysql on localhost, then mysql-proxy does not send any query
to other database.
You don't need to stop mysqld on 127.0.0.1 to see queries on 10.0.0.5,
it should use them round-robin.
http://dev.mysql.com/doc/refman/5.0/en/mysql-proxy-using.html
I tried to reproduce it with a similar config to yours, but it works
just fine.
Norbert
--
Vladimír Rajnyš,
http://www.termsnet.cz
mobil: 773 407 130
tel.: 387 685 152
