You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/20 11:43:00 UTC

[jira] [Commented] (IGNITE-8339) After cluster activation actual partition state restored from WAL may be lost

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

ASF GitHub Bot commented on IGNITE-8339:
----------------------------------------

GitHub user Jokser opened a pull request:

    https://github.com/apache/ignite/pull/3885

    IGNITE-8339 Do not log to WAL partition own during activation.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-8339

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3885.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3885
    
----
commit c8b64bb3a1f3a6c37c00e8406be7bf20fd72b606
Author: Pavel Kovalenko <jo...@...>
Date:   2018-04-20T11:40:41Z

    IGNITE-8339 Do not log to WAL partition own during activation.

----


> After cluster activation actual partition state restored from WAL may be lost
> -----------------------------------------------------------------------------
>
>                 Key: IGNITE-8339
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8339
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.5
>            Reporter: Pavel Kovalenko
>            Assignee: Pavel Kovalenko
>            Priority: Critical
>             Fix For: 2.5
>
>
> On cluster activation we restore partition states from checkpoint and WAL. But before that action we pre-create partitions by ideal assignment on "beforeExchange" phase and own it in case of first or next activation. This partition state change is logged to WAL and override actual last state of partition during restore.
> Possible solutions:
> 1) Pre-create partitions after actual restore.
> 2) Do not log to WAL partition own on pre-create phase.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)