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 --- integration-test/src/test/resources/application.yml | 1 + 1 file changed, 1 insertion(+) (limited to 'integration-test/src/test/resources') diff --git a/integration-test/src/test/resources/application.yml b/integration-test/src/test/resources/application.yml index 793acc6395..f9958651d7 100644 --- a/integration-test/src/test/resources/application.yml +++ b/integration-test/src/test/resources/application.yml @@ -230,6 +230,7 @@ ncmp: hazelcast: cluster-name: cps-and-ncmp-test-caches + instance-config-name: "cps-and-ncmp-hazelcast-instance-test-config" mode: kubernetes: enabled: false -- cgit 1.2.3-korg