[jira] [Commented] (IGNITE-8122) Partition state restored from WAL may be lost if no checkpoints are done

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user Jokser opened a pull request:

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

    IGNITE-8122 Restore partition in state OWNING

    

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

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

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

    https://github.com/apache/ignite/pull/3745.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 #3745
    
----
commit 604ee719b304d0b4cf4caabaa6fa16b5a980e04e
Author: Pavel Kovalenko <jo...@...>
Date:   2018-04-04T09:33:10Z

    IGNITE-8122 Restore partition state to OWNING if unable to read from page memory.

----


> Partition state restored from WAL may be lost if no checkpoints are done
> ------------------------------------------------------------------------
>
>                 Key: IGNITE-8122
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8122
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.4
>            Reporter: Pavel Kovalenko
>            Assignee: Pavel Kovalenko
>            Priority: Minor
>             Fix For: 2.5
>
>
> Problem:
> 1) Start several nodes with enabled persistence.
> 2) Make sure that all partitions for 'ignite-sys-cache' have status OWN on all nodes and appropriate PartitionMetaStateRecord record is logged to WAL
> 3) Stop all nodes and start again, activate cluster. Checkpoint for 'ignite-sys-cache' is empty, because there were no data in cache.
> 4) State for all partitions will be restored to OWN (GridCacheDatabaseSharedManager#restoreState) from WAL, but not recorded to page memory, because there were no checkpoints and data in cache. Store manager doesn't have any allocated pages (including meta) for such partitions.
> 5) On exchange done we're trying to restore states of partitions (initPartitionsWhenAffinityReady) on all nodes. Because page memory is empty, states of all partitions will be restored to MOVING by default.
> 6) All nodes start to rebalance partitions from each other and this process become unpredictable because we're trying to rebalance from MOVING partitions.



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