ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Vinogradov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-1525) Return value for cache operation can be lost with onePhaseCommit
Date Tue, 13 Sep 2016 10:29:20 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15486880#comment-15486880
] 

Anton Vinogradov edited comment on IGNITE-1525 at 9/13/16 10:28 AM:
--------------------------------------------------------------------

All comments fixed, TC and benchs checked.


was (Author: avinogradov):
All comments fixed, TC and benchs checked, 

> Return value for cache operation can be lost with onePhaseCommit
> ----------------------------------------------------------------
>
>                 Key: IGNITE-1525
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1525
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache
>    Affects Versions: ignite-1.4
>            Reporter: Semen Boikov
>            Assignee: Anton Vinogradov
>            Priority: Critical
>             Fix For: 1.8
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message