Forum Discussion
pjcampbell_7243
Cirrus
Apr 09, 2009Would you route mysqld through the BIG IP?
Right now we have our servers hitting our primary mysqld directly.
In the event of an outage, we have to manually change ALL the config files which are pointing at the primary. The other option is to somehow redirect traffic from the IP of the primary to the secondary.
Based on conversation with F5 support, they don't particularly recommend routing local mysql traffic through the BIG IP, however they do not have any reason that it wouldn't work.
Could anyone share any thoughts either way on this? positives or negatives.
The biggest advantage, I see, is that in the event of a fail over (even if it is manual), 2 clicks on the BIG IP will do it, as well as the option for automatic failover.
This is a master/slave setup, not master/master.
- Just wanted to bump this up.
- hoolio
Cirrostratus
We're considering this for a customer's Oracle DB in the same scenario (manual failover to start with). I can't see any issues and do see the advantage of having a constant IP:port for the app servers to reference. - dennypayne
Employee
As long as by "master/slave" you mean that your pool will use priority group activation and send the traffic only to the primary server unless it is down, this should work fine. You just don't want to actively load-balance db writes (reads would be OK I would think). - steve_88008
Nimbostratus
- hoolio
Cirrostratus
I don't think you'd want to have an app doing a DNS lookup to find out which IP address to connect to for SQL calls. The latency involved would probably be a major issue. - JRahm
Admin
Depends on the use case, I suppose. I've used GTM for this function in the datacenter and it works quite nicely.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects