I've double-checked your reproducer and seems it passes on current  master.
Not sure what should I do to fail it. Can you help?

I would like to hear the opinion of other community members, but as for me
it's OK when client node sends cache creation request to cluster and may
fail with it by some reasouns. Server nodes should handle this request and
create cache for themselfs.

On Fri, 10 Aug 2018 at 12:55 Denis Garus <> wrote:

> Hi, Igniters!
> Currently, errors of creation dynamic caches on server nodes and client
> nodes are different.
> If an error occurs on a server node, all cache nodes should revert the
> changes [1].
> If an error occurred on a client node, the client reverts the changes,
> servers nodes start cache.
> In that case, the client node just throws the CacheException [2].
> Is this way correct?
> Maybe we should stop the client node if an error of cache creation occurred
> on it?
> [1]
> [2] the reproducer:
> --
> Sent from:
Maxim Muzafarov

Reply via email to