From 8e46da6c3a7b46a067bf72ebae0be1811ea7f9d0 Mon Sep 17 00:00:00 2001 From: mpriyank Date: Tue, 10 Sep 2024 16:12:28 +0100 Subject: use one hazelcast instance per jvm - updated all the cache(distributed datastructures) to use the same instance config now. - there will be just one instance per JVM now - Better cleanup of hz instance in the testware - Refactored the testware to verify the configs - Expected Impact on lowering the memory usage, less number of TCP communications between members - NOTE: we need to do a full regression as the changes impacts all the use cases which involves cache Issue-ID: CPS-2408 Change-Id: I7564992a9990f44ef3defb4f50cb7d094cad7b92 Signed-off-by: mpriyank --- cps-application/src/main/resources/application.yml | 1 + 1 file changed, 1 insertion(+) (limited to 'cps-application') diff --git a/cps-application/src/main/resources/application.yml b/cps-application/src/main/resources/application.yml index 05b0d09ac5..cf9c4fb009 100644 --- a/cps-application/src/main/resources/application.yml +++ b/cps-application/src/main/resources/application.yml @@ -249,6 +249,7 @@ ncmp: # Custom Hazelcast Config. hazelcast: cluster-name: ${CPS_NCMP_CACHES_CLUSTER_NAME:"cps-and-ncmp-common-cache-cluster"} + instance-config-name: ${CPS_NCMP_INSTANCE_CONFIG_NAME:"cps-and-ncmp-hazelcast-instance-config"} mode: kubernetes: enabled: ${HAZELCAST_MODE_KUBERNETES_ENABLED:false} -- cgit 1.2.3-korg