I've had issues like this in the past, and in the worst situations your services can end up giving your system a ddos.
what i usually do to avoid this, is implement a delay on the connection pool itself, and have each service cycle through a set of delays with a different starting point in the fibonacci sequence. this way if the db server goes down, everyone doesn't try to reconnect at once -- some wait 200ms, others 300, 500, 800, etc. a failure results in slightly longer delay for retry. this reduces the chance of concurrent re-connects. -- 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 http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
