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/12/03 08:56:11 UTC

[jira] [Closed] (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 closed IGNITE-1027.
--------------------------------
    Assignee:     (was: Semen Boikov)

> 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
>             Fix For: 1.5
>
>
> 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)