FYI: I found the conn leak is due to the mysql-connector-python. I started
a post here if anyone is interested:
http://forums.mysql.com/read.php?50,616862,616862#msg-616862
On Friday, July 4, 2014 4:08:40 PM UTC-4, François Schiettecatte wrote:
>
> Hi
>
> Again I think there is a bug
Hi
Again I think there is a bug somewhere in how django handles CONN_MAX_AGE when
it is not set or set to 0, you should not be seeing those sleeping connections.
It is perfectly fine to set CONN_MAX_AGE to some number, though keep it to less
than the wait_timeout in my.cnf. You will still see
Thanks for the tips @Francois! Yeah, I already have this CONN_MAX_AGE set
to 0. I even try some positive number, but there is still Sleep connections
remain after the app is started and running without any traffic. Which is
not what I expect when set to 0 value.
I don't even have fancy background
@cercatrova2, yes, these problems are coming using python3 and the
mysql-connector-python and I am using their "mysql.connector.django".
Currenly I have briefly experimented the default django.db.backends.mysql
with Python3 driver https://github.com/clelland/MySQL-for-Python-3, but I
still see
Hi
I have a little experience with this, and I have posted about this here before.
The "MySQL Connection not available" message will occur when MySQL is dropping
the connection before Django is done with it, ie Django is trying to send
something down a dead connection.
I would look at
On 04/07/14 16:11, Zemian Deng wrote:
@cercatrova2,
Yes,
my original problem also was
(and still is) with "MySQL
Connection not available" after the 8 hours timeout
inactivity on webfaction
@cercatrova2,
Yes, my original problem also was (and still is) with "MySQL Connection not
available" after the 8 hours timeout inactivity on webfaction hosting. I
have to restart it whenever this happens and then problem will go away. My
current workaround is to schedule a dummy crontab to hit my
On 04/07/14 05:04, Zemian Deng wrote:
Hi,
In my django settings.py I have set CONN_MAX_AGE=0 to use
with MySQL DB, which I understood as closing conn after each
request. However when I start a simple "mysite" tutorial with
Hi,
In my django settings.py I have set CONN_MAX_AGE=0 to use with MySQL DB,
which I understood as closing conn after each request. However when I start
a simple "mysite" tutorial with "python manage.py runserver", I see
immediately 3 connections in mysql that will not close but in Sleep mode.
9 matches
Mail list logo
