[
https://issues.apache.org/jira/browse/IGNITE-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-521:
-----------------------------------
Fix Version/s: sprint-4
> Exception is not thrown on near node when TX is failed on primary node.
> -----------------------------------------------------------------------
>
> Key: IGNITE-521
> URL: https://issues.apache.org/jira/browse/IGNITE-521
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: sprint-1
> Reporter: Vladimir Ozerov
> Assignee: Alexey Goncharuk
> Priority: Critical
> Fix For: sprint-4
>
>
> Test scenario:
> 1) Start 2 nodes with TX PARTITIONED_ONLY cache and 0 backups.
> 2) Start continuous query providing a filter which throws exceptions on each
> call.
> 3) Put primary key to cache through "getAndPut()" -> TX is rolled back, you
> receive exception.
> 4) Put near key to cache in the same way -> TX is rolled back, but NO
> EXCEPTION!
> 5) Set backups=1 => step 4 throws an exception as expected.
> 6) Set mode to ATOMIC => step 4 throws an exception as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
