Wierd mysql limits problem

[HalfaBee]

I was working on a script yesterday and the script came up with the max connections error.

I then logged into the DB using the same user with mysql-front and it let me in at the same time the script was failing.

Any comments Starr or other admin?

[Jade Dragon]

mysql-front resides on your computer. You will be able to backup/restore etc with no limitations.

Your webscripts have the questions/connections which are counted toward your limits.

phpMyAdmin may or may not work since it is web based and some larger queries may even time out.

Jade

[HalfaBee]

Thanks jade that didn't make much sense to me.

If I have used all the 3600 connections I can still connect via mysql-front?
That seems really odd.
How can mysql tell the difference between php accesses and mysql-front access.
They should all look similar.
I was doing queries on mysql-front with no problem yet the script could not.
Are these a php limitation or a mysqld limitation

I should have tried using my local mysql to try and connect as well. I will next time.

HalfaBee

[James]

There is little documentation on the specifics on the new mysql limitations, however I believe since there is a wild card hostname for your username, it may be that user@eachhost has the limits impossed on them... meaning if you connect from your home computer it does not count against what your website uses. When mysql 4.1 is released they will have completed their documentation on these things so we will know for sure... I am also hoping they shed some light on how users can monitor their usage as well.

[HalfaBee]

Thanks for the response James.

It seems to be a very hit and miss affair with the limits and how they are reset at the moment.
Are the 3600 connections over the last 60 mins or hour per hour?

Hopefully with 4.1 everything will calm down.
It seems a bit odd having limits that are not able to be monitored.


HalfaBee

[curran]

Originally posted by James
There is little documentation on the specifics on the new mysql limitations, however I believe since their is a wild card hostname for your username, it may be that user@eachhost has the limits impossed on them... meaning if you connect from your home computer it does not count against what your website uses. When mysql 4.1 is released they will have completed their documentation on these things so we will know for sure... I am also hoping they shed some light on how users can monitor their usage as well.

Its incredibly wierd running software that is not ready for prime time (gamma test software !) on production servers. This is generally not "best practise". It is strictly forbidden where I work - and it is forbidden on every platform that we support - UNIX, OS/390 and Wintel. Maybe the production release will give us a break now that we've gamma tested it for them. Has anyone been reporting the problems back to MySQL so that there is a possibility that 4.1 will be clean?

[omatic]

Originally posted by curran
Its incredibly wierd running software that is not ready for prime time (gamma test software !) on production servers.If I may speculate wildly for a second :D I think they wanted the usage limits ASAP, because heavy-hitters were taking the servers down so often (sometimes requiring the mySQL boxes to be rebooted more than once a day!).

Yet after all the fallout from this move, I would have to guess that such an undertaking will not be attempted in the future. ;)

Cheers,
omatic

[omatic]

Originally posted by HalfaBee
Hopefully with 4.1 everything will calm down.
It seems a bit odd having limits that are not able to be monitored. Whoo! I'll second that! I can't wait until there's some sort of 'mySQL stats' ability. *crosses fingers*
omatic

[James]

I again would like to point out that the reason the software is gamma is not because of code quality, mysql.com uses it themselves and call it stable, quoted from their site:

1.5.1 Stepwise Rollout

MySQL is starting from 4.0.6 been labelled gamma, which means that 4.0.x has been available more than 2 months (first in alpha and then in beta) without any found serious hard to fix bugs and should now be ready for production use.

AND

1.5.2 Ready for Immediate Use

All binary releases pass our extensive test suite without any errors on any of the platforms we test on. MySQL 4.0 has been tested on by a large number of users and is in production used by several big sites.


Also, we have conducted our own tests over and over again. We send exactly 36,000 queries to the server and then are maxed out, then one hour later access is completely restored. mysql is perfomming excellently. We have also had a number of requests that we upgrade so people can take advantage of new features.