Transaction not aborted when rollback fails
-------------------------------------------
Key: SEQUOIA-894
URL: https://forge.continuent.org/jira/browse/SEQUOIA-894
Project: Sequoia
Type: Bug
Components: Core
Versions: Sequoia 2.10.4
Reporter: Damian Arregui
Assigned to: Damian Arregui
Fix For: Sequoia 2.10.5
When a rollback fails, for example because of a communication link exception,
the associated transaction is not aborted and potentially remains active
forever in the scheduler.
This can be easily reproduced with MySQL backends:
- Start a transaction and issue a write query.
- Open mysql, run "show processlist" to find the thread executing the
transaction, and kill it.
- If you try to roll back, a connection failure will occur on the client.
- Using "dump scheduler queues" through the console we can check that there is
an active transaction
This is not consistent with the behavior of commit, which does abort the
associated transaction in case of failure.
--
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
