You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Valentin Kulichenko (JIRA)" <ji...@apache.org> on 2017/10/06 21:55:02 UTC
[jira] [Updated] (IGNITE-6575) IgniteCache#get can return stale
value when executed on backup
[ https://issues.apache.org/jira/browse/IGNITE-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Kulichenko updated IGNITE-6575:
----------------------------------------
Issue Type: Improvement (was: Bug)
> IgniteCache#get can return stale value when executed on backup
> --------------------------------------------------------------
>
> Key: IGNITE-6575
> URL: https://issues.apache.org/jira/browse/IGNITE-6575
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 2.2
> Reporter: Valentin Kulichenko
>
> If write sync mode is {{PRIMARY_SYNC}} and {{readFromBackup=true}} (both values are defaults), calling {{get}} right after {{put}} for the same key in the same thread can return stale value. This happens because even local backup is updated asynchronously.
> This is very confusing behavior for a user, would be good to make sure to update local backup synchronously even in {{PRIMARY_SYNC}} mode.
> More details here: http://apache-ignite-developers.2346864.n4.nabble.com/PRIMARY-SYNC-readFromBackup-semantics-td22900.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)