[IGNITE-4887] Support transaction continuation in another thread

• Type: Improvement
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.9
• Component/s: general
• Assignee: Alexey Kuznetsov
• Reporter: Alexey Kuznetsov
• Created: 30/Mar/17 14:45
• Updated: 13/Oct/17 10:49

Description

Consider the following pseudo-code:

        IgniteTransactions transactions = ignite1.transactions();
        Transaction tx = startTransaction(transactions);
        cache.put("key1", 1);
        tx.stop();

And in another thread:

                transactions.txStart(tx);
                cache.put("key3", 3);
                cache.remove("key2");
                tx.commit();

The Api should be implemented , that let you continue transaction in another thread.
method suspend() should mark the transaction as unavailable for further commit.
method resume should resume the transaction.

reason behind the proposal :
Consider the next scenario:
we begin transaction, doing some changes and start async future that will be able to introduce futher changes into transaction and commit it in the end.

Issue Links

• blocks: IGNITE-5831 .NET: Support TransactionScopeAsyncFlowOption.Enabled in TransactionScope
• links to: GitHub Pull Request #2061
• links to: PR
• links to: upsource

Sub-Tasks

• Context switching for optimistic transactions: Resolved
• Implementation of suspend/resume for pessimistic transactions: Resolved
• Thread safety for transaction operations: Resolved
• .NET: Support transaction continuation in another thread: Open