[IGNITE-1525] Return value for cache operation can be lost with onePhaseCommit

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: ignite-1.4
• Fix Version/s: 1.8
• Component/s: cache
• Assignee: Anton Vinogradov (Obsolete, actual is "av")
• Reporter: Semen Boikov
• Created: 22/Sep/15 14:24
• Updated: 03/Jul/18 10:31
• Resolved: 19/Sep/16 15:35

Description

Looks like with onePhaseCommit return value for cache operation can be lost if primary node fails, GridNearTxPrepareResponse with return value is not received, but transaction executes 'check backup' step and finishes without error.

Reproduces in IgniteCachePutRetryTransactionalSelfTest.testInvoke, also added one more test to check return value IgniteCachePutRetryTransactionalSelfTest.testGetAndPut.

Please unmute tests on TC when fixed.

Issue Links

• is related to: IGNITE-3932 Return value for remove or putIfAbsent can be lost with onePhaseCommit
• relates to: IGNITE-8823 Incorrect transaction state in tx manager