Versions Compared

Old Version 1

changes.mady.by.user Priyank Maheshwari

Saved on

compared with

New Version 2

changes.mady.by.user Priyank Maheshwari

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

References

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-2408

Current Instance Configuration

  • As per the current configuration,

    • We have single cluster - exposed using CPS_NCMP_CACHES_CLUSTER_NAME and defaults to cps-and-ncmp-common-cache-cluster

    • Each data structure has its own instance per JVM. So for the below case we have 6 instance per JVM.

Data Structure Name

Configuration Name

Instance Name

1

moduleSyncWorkQueue

defaultQueueConfig

moduleSyncWorkQueue

2

moduleSyncStartedOnCmHandles

moduleSyncStartedConfig

moduleSyncStartedOnCmHandles

3

dataSyncSemaphores

dataSyncSemaphoresConfig

dataSyncSemaphores

4

trustLevelPerCmHandle

trustLevelPerCmHandleCacheConfig

hazelcastInstanceTrustLevelPerCmHandleMap

5

trustLevelPerDmiPlugin

trustLevelPerDmiPluginCacheConfig

hazelcastInstanceTrustLevelPerDmiPluginMap

6

cmNotificationSubscriptionCache

cmNotificationSubscriptionCacheMapConfig

hazelCastInstanceCmNotificationSubscription

Target Instance Configuration

  • What I want to achieve,

    • Cluster would still be the same but want to limit the number of instances.

    • We will have a single Hazelcast instance that has all the configurations of different data structures and we can get hold off a datastructure when needed using that instance.

    • It will be a single instance per JVM.