It is a global scope) Now multiple threads can commit transaction and it will lead to exception. It doesn't refer to my ticket only, but for a current transaction implementation.
пн, 3 июл. 2017 г. в 16:53, Yakov Zhdanov <yzhda...@apache.org>: > What separate ticket do you mean here? I think this is the scope of the > original one. > > --Yakov > > 2017-07-03 16:39 GMT+03:00 ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > > > I've go a test, which illustrates transaction commit fail when multiple > > threads try to commit. As i said, it happenes in mvcc stage. > > > > So we should create a special lock mechanism for all transaction methods. > > In a separate ticket. > > > > пн, 3 июл. 2017 г. в 16:26, Yakov Zhdanov <yzhda...@apache.org>: > > > >> >Consider thread *Th1* started transaction *Tx1*, done some actions, and > >> is > >> >calling commit (GridNearTxLocal#commit -> commitNearTxLocalAsync). And > >> >concurrently thread *Th2 *is calling the same commit on* Tx1*. > >> > >> Alexey, this looks weird to me. IMO, if we talk about proper > >> implementation > >> you should detect all cases of illegal access (e.g. commit from thread > not > >> owning the transaction). > >> > >> --Yakov > >> > > -- > > > > *Best Regards,* > > > > *Kuznetsov Aleksey* > > > -- *Best Regards,* *Kuznetsov Aleksey*
