An interesting case of melt down...
mysql-proxy was up for over two weeks when maintenance on one of the mysql servers had to be performed. Proxy was load balancing among six servers. Once the mysqld was down the mysql-proxy echoed a few dozen times the following error :
mysql> network-mysqld.c.564: write() failed: Connection timed out
network-mysqld.c.1278: network_mysqld_write(CON_STATE_SEND_QUERY_RESULT) returned an error
mysql-proxy became unresponsive for a good while and eventually had to be killed with -9.
Question:
Are those errors indicating to what is went wrong and why mysql-proxy didn't softly skip the disconnected server?
Subject
Views
Written By
Posted
An interesting case of melt down...
4064
October 09, 2007 07:56PM
2391
October 10, 2007 03:44AM
2357
October 10, 2007 12:12PM
2228
October 22, 2007 04:40AM
2309
October 28, 2007 03:25PM
2253
October 29, 2007 05:03AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.