You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2015/06/15 22:49:01 UTC
[jira] [Updated] (IGNITE-621) Need to add automatic retry to avoid
partial update exception and topology exception
[ https://issues.apache.org/jira/browse/IGNITE-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Goncharuk updated IGNITE-621:
------------------------------------
Summary: Need to add automatic retry to avoid partial update exception and topology exception (was: Need to add automatic retry to avoid partial update exception)
> Need to add automatic retry to avoid partial update exception and topology exception
> ------------------------------------------------------------------------------------
>
> Key: IGNITE-621
> URL: https://issues.apache.org/jira/browse/IGNITE-621
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: sprint-2
> Reporter: Alexey Goncharuk
>
> Currently atomic cache throws a partial update exception when primary node leave before response is received.
> We can automatically retry update in the following cases:
> # Unconditional cache operation (put, remove)
> # Idempotent conditional cache operations (putIfAbsent, replace) can be reinforced if value from primary node is forcibly pushed to backups regardless whether update took place or not
> # For entry processors repeat should be done if cache configuration flag (should be introduced, defaults to false) is set to true.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)