Red Hat Bugzilla – Bug 1024934
1PC can cause a window of inconsistency with L1 invalidation
Last modified: 2013-12-10 06:30:11 EST
William Burns <email@example.com> updated the status of jira ISPN-3518 to Coding In Progress
Radim Vansa <firstname.lastname@example.org> made a comment on jira ISPN-3518
I know it's already fixed, but is it really a bug? The described scenario does not break the serializability property of the transactions - the outcome is the same as if tx2 was executed before tx1. Could you describe the scenario where it does break some expected property?