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 Govorukhin (JIRA)" <ji...@apache.org> on 2017/06/02 08:58:04 UTC
[jira] [Assigned] (IGNITE-5386) Inactive mode must be forced on
starting up grid with persistence is enabled
[ https://issues.apache.org/jira/browse/IGNITE-5386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy Govorukhin reassigned IGNITE-5386:
------------------------------------------
Assignee: Dmitriy Govorukhin (was: Sergey Chugunov)
> Inactive mode must be forced on starting up grid with persistence is enabled
> ----------------------------------------------------------------------------
>
> Key: IGNITE-5386
> URL: https://issues.apache.org/jira/browse/IGNITE-5386
> Project: Ignite
> Issue Type: Task
> Components: persistence
> Reporter: Sergey Chugunov
> Assignee: Dmitriy Govorukhin
> Labels: important
> Fix For: 2.1
>
>
> h2. Notes
> There is an issue in grid startup documented in IGNITE-5363.
> In a nutshell it is caused by double initialization of database memory and disk structures when grid started in inactive mode gets activated.
> To prevent this grid with persistence enabled must be started in the following order
> # Inactive mode must be forced if persistence is enabled (if node is starting up in active mode and persistence is enabled, an exception must be thrown).
> # During starting the node database is left uninitialized.
> # When user triggers activating the cluster, database memory and disk structures are initialized on all nodes.
> h2. Acceptance Criteria
> # Inactive mode is forced on grid startup when persistence is enabled.
> # New node join scenario is properly covered.
> # All persistence-related tests are passing, no new test failures are added.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)