Hey guys,
So I was wondering if anyone has come across a similar problem in their career of web development.
At the moment, we have several web servers which are in rotation (two currently stable) that have a load balancer pointed at them.
The strange thing is, whenever we stick a new server in (same architecture). Once it's put into rotation after around half an hour or so, we start seeing a lot of threads being created in the MySQL process list. These are NULL's, eventually - this brings the site to a stand still and we have to revert back to the previous two servers.
We are running some legacy code on PHP 5.3.1 with the OS being Centos 6.X
It's rather peculiar. I have tried checking for pconnect, which isn't set anywhere and I've been checking for persistent connections / closing off connections, all to no avail.
The strange thing is it works fine for individual servers or those two servers. But when we stick a third in this problem kicks in, which makes debugging a real pain in the backside.
Any clues?
So I was wondering if anyone has come across a similar problem in their career of web development.
At the moment, we have several web servers which are in rotation (two currently stable) that have a load balancer pointed at them.
The strange thing is, whenever we stick a new server in (same architecture). Once it's put into rotation after around half an hour or so, we start seeing a lot of threads being created in the MySQL process list. These are NULL's, eventually - this brings the site to a stand still and we have to revert back to the previous two servers.
We are running some legacy code on PHP 5.3.1 with the OS being Centos 6.X
It's rather peculiar. I have tried checking for pconnect, which isn't set anywhere and I've been checking for persistent connections / closing off connections, all to no avail.
The strange thing is it works fine for individual servers or those two servers. But when we stick a third in this problem kicks in, which makes debugging a real pain in the backside.
Any clues?
