You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (JIRA)" <ji...@apache.org> on 2016/08/17 11:15:20 UTC
[jira] [Commented] (IGNITE-1525) Return value for cache operation
can be lost with onePhaseCommit
[ https://issues.apache.org/jira/browse/IGNITE-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424305#comment-15424305 ]
Anton Vinogradov commented on IGNITE-1525:
------------------------------------------
According to face-to-face review with Semen decided to add more benchmarks checks speed of OPC.
And, in case some problems will be found, need to refactor final solution
Possible refactoring ways:
1) Send ack not at each OPC.
2) Fix failover to make fullscan at failure instead of usage aditional map
> 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)