ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Vinogradov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2864) Need update local store from primary and backups
Date Wed, 20 Apr 2016 15:32:25 GMT

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

Anton Vinogradov commented on IGNITE-2864:
------------------------------------------

Eventually I've added system property IGNITE_LOCAL_STORE_KEEPS_PRIMARY_ONLY and set it false
by default. It means that new behavior will be active by default.
Also I added more tests for old and new behavior.
In case user will try to combine nodes with versions "before" and "after" fix with configured
local store he will gain warning:
"Since Ignite 1.5.15 Local Store keeps primary and backup partitions. To keep primary partitions
only please set system property IGNITE_LOCAL_STORE_KEEPS_PRIMARY_ONLY  to 'true'."
  

> 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)

Mime
View raw message