[
https://issues.apache.org/jira/browse/IGNITE-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246952#comment-15246952
]
Dmitriy Setrakyan commented on IGNITE-2864:
-------------------------------------------
Is this feature optional? I think it should be set through configuration and
should be turned off by default, because it only makes sense for per-JVM
CacheStore and not for centralized databases. If it has been made configurable,
what is the name of the configuration property?
> 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)
