You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2015/10/07 08:11:27 UTC

[jira] [Updated] (IGNITE-1027) Possible data loss in replicated cache on unstable topology.

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

Semen Boikov updated IGNITE-1027:
---------------------------------
    Fix Version/s:     (was: ignite-1.5)

> Possible data loss in replicated cache on unstable topology.
> ------------------------------------------------------------
>
>                 Key: IGNITE-1027
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1027
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Sergi Vladykin
>            Assignee: Semen Boikov
>
> In test IgniteCacheClientQueryReplicatedNodeRestartSelfTest we have 4 data nodes with replicated caches and single client-only node, which runs SQL queries against those data nodes. Background threads restarting data nodes. When we restart 2 of 4 data nodes everything is fine, when 3 of 4 then eventually query returns inconsistent result and cache size returns smaller values than expected. Since we use rebalance mode SYNC, such a data loss should not happen.



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