[ https://forge.continuent.org/jira/browse/SEQUOIA-903?page=comments#action_13824 ]
Damian Arregui commented on SEQUOIA-903: ---------------------------------------- Not trivial to fix. Problems appear when a persistent connection has been closed through the CLI and then the client fails over from one controller to the other. In this case when a new request comes in we just lazily open a new persistent connection. We do not keep the information that the connection has been closed. A similar issue affects administrative transaction abort. See SEQUOIA-895. > Add a dump connections and a close connection commands (persistent > connections only) > ------------------------------------------------------------------------------------ > > Key: SEQUOIA-903 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-903 > Project: Sequoia > Type: New Feature > Components: CLI Console > Versions: Sequoia 2.10.4 > Reporter: Damian Arregui > Assignee: Damian Arregui > Priority: Critical > Fix For: Sequoia 2.10.7, Sequoia 3.0 beta3 > > > This is targeted only at persistent connections (at least for the moment). > Rationale is that even if the application screwed things up it is not > acceptable/desirable to "shutdown force" and bring the cluster up from a > dump. The administrator may rather choose to close the connections preventing > a safe shutdown. -- 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 [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
