Hi Evgenii,
Later investigations, we found that this is happening due to the near-cache
"rdrs" not released from entries i.e. GridDhtCacheEntry objects.
When near-cache entry is getting evicted from a ignite-client node; it is
not clearing the rdrs from Server. Due to these rdrs not empty, the
Hi,
>From logs, I see that all server nodes are pinging node on host 10.180.48.14
all the time. It can be caused by the lack of the connection between part of
the nodes(for example, if node 10.180.48.14 can't directly communicate with
client nodes). I think that client nodes might ask server
Hi Evgenii,
We are using EntryProcessor to update/insert objects into cache, in addition
to GET cache object calls. Multiple services are making these calls using
IgniteClients. We have enabled NearCache on Ignite Clients.
Size of the objects: We will figure out today, and we will post it here
Hi Prasad,
What operations do you run on the cluster? What is the size of objects? Is
it possible to share full logs from nodes? Do you have some kind of small
reproducer for this issue? It would be really helpful.
Thanks,
Evgenii
пн, 5 окт. 2020 г. в 07:53, Prasad Pillala :
> Hi,
>
>
>
>
Hi,
evictDataPage() always leads to ignite cluster blocked, due to some reason.
This method does not seem to consider the freelist, which is still have
some/many pages available. But evictDataPage() still trying to evict few
entries from filled pages, and after sometime (in few mins, after
