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

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

GitHub user Jokser opened a pull request:

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

    IGNITE-9419 Async wait for caches registration and save during PME.

    

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

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

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

    https://github.com/apache/ignite/pull/4674.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 #4674
    
----
commit 410a9a944f7cc98388b4c2bfa97a88f424a32c07
Author: Pavel Kovalenko <jokserfn@...>
Date:   2018-09-03T16:50:29Z

    IGNITE-9419 Async wait for caches registration and save during PME.

----


> Avoid saving cache configuration synchronously during PME
> ---------------------------------------------------------
>
>                 Key: IGNITE-9419
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9419
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.5
>            Reporter: Pavel Kovalenko
>            Priority: Major
>             Fix For: 2.7
>
>
> Currently, we save cache configuration during PME at the activation phase 
> here 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.CachesInfo#updateCachesInfo
>  . We should avoid this, as it performs operations to a disk. We should save 
> it asynchronously or lazy.



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

Reply via email to