[Twisted-Python] Consensus on how to handle "MySQL server has gone away"
Augusto Mecking Caringi
augustocaringi at gmail.com
Wed Oct 3 09:36:07 EDT 2012
On Wed, Oct 3, 2012 at 8:27 AM, Itamar Turner-Trauring
<itamar at itamarst.org> wrote:
> On 10/03/2012 04:28 AM, Phil Mayers wrote:
>> I think the behaviour it should be aiming for is clear:
>> 1. Test each connection with "good_sql" before beginning the user
>> interaction/query
>
> The problem is that this adds latency; this can add up to quite a
> slowdown if your database server is on a remote server and you're doing
> lots of single queries (as opposed to runInteraction).
Hi!
Sometime ago I faced some related problems and I found this code,
"ReconnectingConnectionPool":
http://www.gelens.org/2009/09/13/twisted-connectionpool-revisited/
What are your opinion about it?
--
Augusto Mecking Caringi
More information about the Twisted-Python
mailing list