[IGNITE-11697] Suspended optimistic transaction automatically resumes to last thread after a timeout.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7
• Fix Version/s: 2.8
• Labels: iep-34
• Assignee: Aleksey Plekhanov
• Reporter: Aleksey Plekhanov
• Created: 08/Apr/19 15:36
• Updated: 13/Aug/19 10:23
• Resolved: 23/May/19 11:53

Description

This leads to unpredictable results from a user's point of view.

Reproducer:

 

public class IgniteTxSuspendAndTimeoutTest extends GridCommonAbstractTest {
    @Test
    public void testSuspendAndTimeout() throws Exception {
        Ignite ignite = startGrid(0);

        IgniteCache cache = ignite.createCache(new CacheConfiguration<>().setName("c").setAtomicityMode(TRANSACTIONAL));

        Transaction tx1 = ignite.transactions().txStart(OPTIMISTIC, TransactionIsolation.REPEATABLE_READ, 100, 0);

        cache.put(1, 1);

        tx1.suspend();

        assertNull(cache.get(1)); // Pass here.

        doSleep(200);

        assertNull(cache.get(1)); // Fail here. But we don't expect any explicitly running transaction at this point.
    }
}

 

 

Issue Links

• is caused by: IGNITE-7481 Suspended transaction rollbacs incorrectly
• is caused by: IGNITE-6827 Configurable rollback for long running transactions before partition exchange
• links to: GitHub Pull Request #6505
• links to: TC