Hi Jonas, Just wondering if you were able to characterize the behavior and had any ideas for gracefully handling RDS failover. From what I'm seeing, RDS will not cause errors, but will simply hang, so SQLA doesn't hit its "optimistic disconnect handling" (http://docs.sqlalchemy.org/en/latest/core/pooling.html#disconnect-handling-optimistic) handler.
Have you found a simple method of identifying failover but not a slow query? Would be super useful for us and I'm guessing other folks using SQLA + RDS. (We're also using Postgres.) - Josh On Saturday, October 18, 2014 at 5:42:32 AM UTC-7, Jonas Oscarsson wrote: > > Thanks for the tip, we haven't tried that yet although I think we would > have the same behavior as it seems to be the next connection after the > database is down that hangs (no matter if it's a SELECT 1 or an actual > query). > > On Fri, Oct 17, 2014 at 5:38 PM, Jonathan Vanasco <[email protected] > <javascript:>> wrote: > >> Have you tried a Pessimistic Disconnect strategy? >> >> >> http://docs.sqlalchemy.org/en/latest/core/pooling.html#dealing-with-disconnects >> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "sqlalchemy" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/sqlalchemy/NANPH1QWgMM/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/sqlalchemy. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
