Random Response corruption about tornado-mysql HOT 3 CLOSED

What could be the issue

Multiple threads use same pool, or multiple coroutine use same connection concurentlly, timeout happen during waiting result, etc...

how do I solve it?

Review your code carefully, and check one connection is not used from multi coroutine concurrently,
don't reuse connection without reading full result (this happens when timeout especially).

from tornado-mysql.

Thanks for the reply methane.

I have been reviewing the code, and I haven't been able to find any code where a connection is being used concurrently by multiple co-routines concurrently.(as per my knowledge :)).

The general way by which we communicate with the database is

cur = pool.execute(query, [arguments])
OR
cur = txn.execute(query, [arguments]), where txn denotes a Transaction object

followed by cur.fetchone() or a cur.fetchall().

Could you please provide me with a few code examples where-in connections are used concurrently, not sure if driver has functions to do this?

Since our database has grown is size, could this be because cur.fetchall() is failing because of memory pressure.

Also,
all connections to the database are in a try and exception block with adequate logging, so shouldn't timeout be raising an operational error, which would then get printed? Unfortunately not seeing any logs regarding the same, and hence am confused.

from tornado-mysql.

I don't have energy and time for this project.
I recommend you to use aiomysql instead of this.

Tornado can use asyncio libraries now.
So this project is only for dying language: Python 2.

from tornado-mysql.