Hi All, We have recently enabled Eviction on Ignite server nodes. We were using ignite nearcache for ignite client nodes.
Due to nearcache, the server side cache-entries are not getting evicted. Eventually this leads to off-cache full, and "Too many attempts to evict data page" error and ignite cluster stopped responding. We have given enough memory to ignite server nodes i.e. 4+4gb for heap and off-heap. >From debugging the server code, it looks like the near-cache enforces the entries to maintain the client-node id; and due to this those entries are not getting evicted from server. When the clientside the entries got evicted (with clientside LRU eviction), it seems the client-node reference in serverside entry is not getting cleared. Hence after sometime it leads to ignite getting blocked. This is consistently happening. Either I am doing some thing wrong with the ignite configurations, OR there is a bug in the ignite with this combination. Can you please guide me, on how to find resolution to this problem. Thanks, Prasad -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
