[
https://issues.apache.org/jira/browse/IGNITE-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16627398#comment-16627398
]
ASF GitHub Bot commented on IGNITE-9418:
----------------------------------------
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/4827
IGNITE-9418 initialize cache persistent storage concurrently.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9418
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4827.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 #4827
----
commit 14a06ea3dea5cfc7cab9e499e8b54759554b36fd
Author: Evgeny Stanilovskiy <estanilovskiy@...>
Date: 2018-09-25T13:49:29Z
IGNITE-9418 initialize cache persistent storage concurrently.
----
> Avoid initialize file page store manager for caches during PME synchronously
> ----------------------------------------------------------------------------
>
> Key: IGNITE-9418
> URL: https://issues.apache.org/jira/browse/IGNITE-9418
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.5
> Reporter: Pavel Kovalenko
> Priority: Critical
> Fix For: 2.8
>
>
> Currently, we do creation for partition and index files during PME for
> starting caches at the beginning of
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#readCheckpointAndRestoreMemory
> method.
> We should avoid this because sometimes it took a long time as we perform
> writing to disk.
> If the cache was registered during PME we should initialize page store lazy
> or asynchronously.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
