Forum Discussion
MySQL active connection never bleed off to other pool member
I am running galera MySQL behind F5 with
performance Layer 4
type and i have setup 3 mysql node in pool member with Priority
so only 1 mysql node will be used and other two will be standby.
So everything was good but i found today when i shutdown Primary node which was active and i found my application break and when i have checked logs found:
(2006, "MySQL server has gone away (error(104, 'Connection reset by peer'))")
So solution was restart application, look like active member mysql connection not bleeding off to other pool member, what is wrong with my setup?
@amintej,
FYI, i have disabled PVA = None and still i am seeing error, so look like that is not an issue.
- amintejCirrus
Ok, and SNAT and automap IPs are in the same network? Maybe you have an asymetric routing problem. You can check it using
tmsh show sys connections
- AjitAltostratus
Satish,
In your pool settings you should try to change your action-on-service-down from "reset" to "reselect".
That should do it for you.
Regards,
Ajit
Recent Discussions
Related Content
* 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