-
Task
-
Resolution: Done
-
Critical
-
30.0.0.Final, 31.0.0.Final
-
None
Currently, our cloud tooling configures clustering in the cloud using a 'replicated' cache mode which is suboptimal as it does not scale.
Such cache mode does not scale and is not suited for applications in the cloud that are supposed to be scalable. In this mode Infinispan replicates all entries in the cache to all nodes in the cluster. It doesn't scale, as adding new nodes does not enlarge the cluster capacity.
The cache mode that scales is the 'distributed' cache. In order to use this cache mode efficiently the server needs to provide the ownership information to the load-balancer and the load-balancer needs to respect the routing information provided by the application server.
With the WFLY-16043 already implemented, the server now has the ability to provide the affinity within a cookie, with the fix for CLOUD-4173 the server node now knows it's pod name which is used for routing.
The server needs to be fixed to no longer attach the routing information where it's never parsed CLOUD-4174.
This Jira is to ensure our documentation explains how to configure things correctly, while the subsequent work will make these the defaults in our tooling.
- clones
-
JBEAP-25999 Document how to optimize cloud clustering configuration created by our tooling to be scalable
- New