Currently we have context switching implemented for optimistic transactions
So, the next step is to implement it for pessimistic transactions :
The problem with them lies in *IgniteTxAdapter#threadId*. Thread id is
transferred between nodes by GridDistributedTxPrepareRequest when key is
When we suspend and resume transaction, thread id is got changed locally,
but not on remote nodes.
After studying the code, it seemed we can eliminate thread id from
For that reason, i want to start implementing additional tests, that will
cover transaction logic. Tickets would be created for them.
Later on I will provide test scenarious and send you. *Will appreciate any
ideas from you on new tests, thanks!*
It will be the first step. The next one will be refactoring and eliminating
thread id. What do you think ?