[ https://forge.continuent.org/jira/browse/SEQUOIA-1144?page=comments#action_15318 ]
Gilles Rayrat commented on SEQUOIA-1144: ---------------------------------------- Solution is to stop informing other connections about the failure. If the controller is really down, they will notice anyway > IOException during (re)connection to a controller disconnects all established > connections to this controller > ------------------------------------------------------------------------------------------------------------ > > Key: SEQUOIA-1144 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-1144 > Project: Sequoia > Type: Bug > Components: JDBC Driver > Reporter: Gilles Rayrat > Assignee: Gilles Rayrat > > > When trying to connect, in Driver#connectToNextController(url), if the driver > receives an IOException, it will inform all other connections about its > failure and disconnect them > This intended behavior was a kind of optimization, where the first client > getting an error informs all others so failover is faster. > The drawback is that a transient problem, or an error that doesn't concern > all connections (eg. Too Many Open files) will cancel all other potentially > good connections and make them reconnect. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://forge.continuent.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ Sequoia mailing list Sequoia@lists.forge.continuent.org https://forge.continuent.org/mailman/listinfo/sequoia
