[ https://forge.continuent.org/jira/browse/SEQUOIA-352?page=all ] Damian Arregui closed SEQUOIA-352: ----------------------------------
> Race condition in commit and rollback failover implementation > ------------------------------------------------------------- > > Key: SEQUOIA-352 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-352 > Project: Sequoia > Type: Bug > Components: Core > Versions: Sequoia 2.6.1 > Environment: Configuration with at least two controllers. > Reporter: Damian Arregui > Assignee: Damian Arregui > Fix For: Sequoia 2.7 > > Time Spent: 1 day > Remaining: 0 minutes > > It's pretty hard to come by this issue since it depends on the exact timing > of the transparent failover process. > The scenario is as follows: > 1 - There is an on-going transaction in the cluster > 2 - Driver sends a commit to controller 1 > 3 - Commit is scheduled on both controllers > 3 - Controller 1 fails while executing the commit > 4 - Driver automatically re-connects to controller 2 and finds the existing > transactional context before Controller 2 finishes executing the commit > 5 - Controller 2 finishes executing the commit and removes the transactional > context > 6 - Driver automatically re-sends a commit but the transactional context is > missing which causes an error -- 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
