[
https://issues.apache.org/jira/browse/IGNITE-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250146#comment-15250146
]
Dmitriy Setrakyan commented on IGNITE-2864:
-------------------------------------------
Can you explain why you decided to use a system property instead of regular
configuration property?
Also, I am not sure I like the name, because this property is not about the
local store, but about the cache store in general. I think it should be named
{{isCentralizedStore}} and should be {{true}} by default. If store is
centralized, then there is no need to write backups to the store. On the other
hand, if store is local to a node, then it should have both, primary and backup
copies for the purpose of recovery.
Do you agree?
> 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)
