Hi,
I have four server nodes and six client nodes on ignite cluster. I am using
ignite 2.10 version.
Some operations are failing due to the CacheStoppedException exception on
the server nodes. This has become a blocker issue.
Could someone please help me to resolve this issue.
*Cache Configuration
Hi, Akash
You can obtain such a case, for example when you have several instances and :
inst1:
cache = inst1.getOrCreateCache("cache1");
after inst2 destroy calling:
cache._some_method_call_
inst2:
inst2.destroyCache("cache1");
or shorter: you still use instance that already destroyed, yo
Hi Zhenya,
Thanks for the quick response.
I believe you are talking about ignite instances. There is
single ignite using in application.
I also want to point out that I am not using destroyCache() method
anywhere in application.
I will set IGNITE_QUIET = false and try to grep the required logs.
Using Ignite 2.10.0
We had a frustrating series of issues with Ignite the other day. We're
using a 4-node cluster with 1 backup per table and cacheMode set to
Partitioned, and write behind enabled. We have a client that inserts data
into caches and another client that listens for new data in thos
Meanwhile I grep the logs with the next occurrence of cache stopped
exception,can someone highlight if there is any known bug related to this?
I want to check the possible reason for this cache stop exception.
On Mon, Sep 6, 2021 at 6:27 PM Akash Shinde wrote:
> Hi Zhenya,
> Thanks for the quick
plz share somehow these logs, if you have no ideas how to share, you can send
it directly to arzamas...@mail.ru
>Meanwhile I grep the logs with the next occurrence of cache stopped
>exception,can someone highlight if there is any known bug related to this?
>I want to check the possible reason