Cache start ordering during cluster activation

[Pavel Kovalenko]

Hello Igniters,

Currently order of cache starts/stops operations is not determined during cluster activation.
Some of the cache components can be depended on system or utility caches. If such component starts earlier than system cache on what it's depended, it can lead to unpredictable errors (e.g. NullPointerException)
I would like to introduce strict order of cache start/stop operations as it is already implemented during normal node join process.
If we form cache start requests they should be ordered (first we should start system caches then user), for cache stop requests order should be reverse (first user caches then system).

[Alexey Goncharuk]

Agree,

Since we rely on cache start order during the node start, the same order
should be preserved during activation.

2017-07-21 15:24 GMT+03:00 Jokser <[hidden email]>:

> Hello Igniters,
>
> Currently order of cache starts/stops operations is not determined during
> cluster activation.
> Some of the cache components can be depended on system or utility caches.
> If
> such component starts earlier than system cache on what it's depended, it
> can lead to unpredictable errors (e.g. NullPointerException)
> I would like to introduce strict order of cache start/stop operations as it
> is already implemented during normal node join process.
> If we form cache start requests they should be ordered (first we should
> start system caches then user), for cache stop requests order should be
> reverse (first user caches then system).
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/Cache-start-ordering-
> during-cluster-activation-tp19910.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>