You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Setrakyan (JIRA)" <ji...@apache.org> on 2016/05/06 17:44:12 UTC

[jira] [Commented] (IGNITE-2864) Need update local store from primary and backups

    [ https://issues.apache.org/jira/browse/IGNITE-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274427#comment-15274427 ] 

Dmitriy Setrakyan commented on IGNITE-2864:
-------------------------------------------

Let me summarize the new behavior, just so we are on the same page:
# All stores with `@CacheLocalStore` annotation will persist primary and backup copies by default.
# This behavior can be turned off if a user adds `IGNITE_LOCAL_STORE_KEEPS_PRIMARY_ONLY` system property.
# No new configuration properties have been added.

If the above is correct, then I think this change makes sense.

> Need update local store from primary and backups
> ------------------------------------------------
>
>                 Key: IGNITE-2864
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2864
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Semen Boikov
>            Assignee: Anton Vinogradov
>             Fix For: 1.6
>
>
> Now cache local store is updated only from primary nodes, this means that data can be lost if primary node is not re-started after crash. Need fix it and update store from primaries and backups if store is local (for both tx and atomic caches).
> This test should work:
> - cache with 1 backup, two server nodes
> - execute cache put for key K
> - stop both nodes
> - restart only node which was backup for K
> - load data from local sore, update for K should be restored



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