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] [Updated] (IGNITE-2893) Atomic structures should not use transactions
Date Mon, 05 Sep 2016 11:20:20 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Semen Boikov updated IGNITE-2893:
---------------------------------
    Fix Version/s:     (was: 1.8)
                   2.0
       Issue Type: Task  (was: Bug)

This change looks risky: as far as I know, currently in atomic cache EntryProcessor can be
applied twice in case of primary node failure. Need carefully review cache usages for data
structures implementation. Let's move it to 2.0 release.

> Atomic structures should not use transactions
> ---------------------------------------------
>
>                 Key: IGNITE-2893
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2893
>             Project: Ignite
>          Issue Type: Task
>          Components: data structures
>    Affects Versions: 1.5.0.final
>            Reporter: Valentin Kulichenko
>            Assignee: Edouard Chevalier
>              Labels: newbie
>             Fix For: 2.0
>
>
> Currently atomic structures like {{AtomicReference}}, {{AtomicLong}} and others use transactional
caches and explicit transactions under the hood. This seems redundant, because can be replaced
with atomic cache and {{invoke}} operations with {{EntryProcessor}}.



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

Mime
View raw message