This is the test i am performing: 1. I have an Ignite Cluster of 3 Server Nodes running in Kubernetes. (the cluster is created using a StatefulSet) 2. Once the cluster is up i use a Deployment to run 5 pods each with a Client Node that performs put operations on my cache. 3. Once i see in the logs "Page-based evictions started. Consider increasing 'maxSize' on Data Region configuration: default" on all 3 Server Nodes i delete the deployment, thus stopping the put opperations. 4. Once the deployment is deleted i restart node-2 from the cluster and once it is up again i wait for it to finish rebalancing. 5. The result of the test so far is that entries are missing from node-2 after the rebalance is complete.
Log Files before the restart: node-0.log <http://apache-ignite-users.70518.x6.nabble.com/file/t2660/node-0.log> node-1.log <http://apache-ignite-users.70518.x6.nabble.com/file/t2660/node-1.log> node-2.log <http://apache-ignite-users.70518.x6.nabble.com/file/t2660/node-2.log> Log Files after the restart: node-0.log <http://apache-ignite-users.70518.x6.nabble.com/file/t2660/node-0.log> node-1.log <http://apache-ignite-users.70518.x6.nabble.com/file/t2660/node-1.log> node-2.log <http://apache-ignite-users.70518.x6.nabble.com/file/t2660/node-2.log> I want to use the cluster to store web-session and i have ~400 request per second of cahe read and put operation. Would disabling the page eviction for the default data region end up and getting OOM Exceptions? If no, i will try and disable it as you suggested and perform more tests. Thanks, Alex. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
