mysql-proxy-discuss team mailing list archive

[Chris Adams <chris@xxxxxxxxxxxxxx>]

I'm working with an AWS RDS instance which has fairly low DNS TTLs as part of their failover mechanism. I'm evaluating mysql-proxy for connection pooling but was wondering about the best strategy for dealing with IP changes: the backend address is read-only and resolved at startup - is there any way to either force a lookup or simply cause mysql-proxy to terminate so it can be restarted automatically? Since these changes usually indicate something has broken, a brief failover interval is tolerable. 

Chris