I have a scala akka app which is using Ignite to store data. I am using
Ignite SDK ignite-spring.2.6.0 to connect to Ignite cluster. Ignite has 3
nodes in the cluster.
The app has an endpoint which gets the data from ignite cluster.
In normal operation the request to the app is getting the correct
directed to the
newly added/restarted node till the rebalance operation is completed
successfully..?
Is it side effect of the migration activity from Apache Ignite 2.4.0 to 2.6.0..?
Thanks and Regards,
Shrikant Sonone
Schlumberger.
Hi All,
I have design question about Ignite web session clustering.
I have springboot app with UI. It clustered app ie multiple instance of
springboot app behind the load balancer. I am using
org.apache.ignite.cache.websession.WebSessionFilter()to intercept request and
create\manage session f
