You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Pavel Kovalenko (JIRA)" <ji...@apache.org> on 2017/07/25 13:57:00 UTC

[jira] [Updated] (IGNITE-5830) Introduce cache start & stop order on cluster activation

     [ https://issues.apache.org/jira/browse/IGNITE-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Kovalenko updated IGNITE-5830:
------------------------------------
    Description: 
Some of the cache components can rely on system/utility caches during start operation, but the order of cache start & stop on cluster activation is not determined. So there can be situation that user cache was started first than system cache and it can lead to unexpected problems.
We should start system & utility caches in first order on cluster activation and stop it in last order on cluster deactivation.

  was:
Some of the cache components can rely on system/utility caches during start operation, but the order of cache start & stop on cluster activation is not determined. So there can be situation that user cache started first than system cache and it can lead to unexpected problems.
We should start system & utility caches in first order on cluster activation and stop it in last order on cluster deactivation.


> Introduce cache start & stop order on cluster activation
> --------------------------------------------------------
>
>                 Key: IGNITE-5830
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5830
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 2.1
>            Reporter: Pavel Kovalenko
>            Assignee: Pavel Kovalenko
>             Fix For: 2.2
>
>
> Some of the cache components can rely on system/utility caches during start operation, but the order of cache start & stop on cluster activation is not determined. So there can be situation that user cache was started first than system cache and it can lead to unexpected problems.
> We should start system & utility caches in first order on cluster activation and stop it in last order on cluster deactivation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)