ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1525) Return value for cache operation can be lost with onePhaseCommit
Date Tue, 13 Sep 2016 12:33:21 GMT

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

Semen Boikov commented on IGNITE-1525:
--------------------------------------

Hi Anton,

I think that at least it makes sense to add tests for nethods which return boolean (putIfAbsent/remove).
If tests will fail, then we need to understand why, probably it can be easily fixed as part
of this fix.

Thanks!

> 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