AbstractScheduler.abortRemainingActiveTransactions will stop aborting
transactions at the first failing abort.
--------------------------------------------------------------------------------------------------------------
Key: SEQUOIA-1025
URL: https://forge.continuent.org/jira/browse/SEQUOIA-1025
Project: Sequoia
Type: Bug
Versions: Sequoia 2.10.9
Reporter: Stephane Giron
Assigned to: Stephane Giron
Fix For: sequoia 2.10.10
As a transaction could be in the list of transactions that should be aborted by
the specified method but can be committed / rolled back in parallel by the
client application, the 2nd abort would fail (No transaction metadata found, or
equivalent), but in that case, other remaining transactions would not be
aborted, which, in case this would occur while disabling a backend, would set
the backend to the UNKNOWN state.
This would then require to resynchronize the backend, whereas it should not
have been needed.
--
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
