Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

FAQ: What is the recommended infinispan configuration setting in production in MDM?
Answer
Assuming that in a production environment, schema changes are made during a downtime and all the nodes in a cluster are restarted after the schema change, the infinispan cache configuration can be changed to ensure that the objects have a longer lifespan and the check for lifespan can be at a longer interval. The following can be changed in a production environment:

<replicated-cache name="DATA_OBJECTS" statistics="true" mode="SYNC" remote-timeout="20000">
                              <locking isolation="READ_COMMITTED" acquire-timeout="60000" write-skew="false" concurrency-level="5000" 
                                        striping="false" />
                              <transaction
                                        transaction-manager-lookup="org.infinispan.transaction.lookup.GenericTransactionManagerLookup"
                                        stop-timeout="30000" auto-commit="true" locking="OPTIMISTIC" mode="NON_XA" />
                              <state-transfer enabled="false" />
                              <eviction strategy="LRU" max-entries="2000000" />
                              <expiration interval="5000" lifespan="3600000" />
                    </replicated-cache>
                    
Changing lifespan 3600000 (1 hour) to a day (86400000) and interval 5000 ( 5 seconds) to 300000 (5 minutes)
<replicated-cache name="DATA_OBJECTS" statistics="true" mode="SYNC" remote-timeout="20000">
                              <locking isolation="READ_COMMITTED" acquire-timeout="60000" write-skew="false" concurrency-level="5000" 
                                        striping="false" />
                              <transaction
                                        transaction-manager-lookup="org.infinispan.transaction.lookup.GenericTransactionManagerLookup"
                                        stop-timeout="30000" auto-commit="true" locking="OPTIMISTIC" mode="NON_XA" />
                              <state-transfer enabled="false" />
                              <eviction strategy="LRU" max-entries="2000000" />
                              <expiration interval="300000" lifespan="86400000" />
                    </replicated-cache>

The same change can be done to the following cache items too: DISABLE_WHEN_LOCK, DATA_OBJECTS, REPOS_OBJECTS caches.
​​

More Information
1) In MDM 10.2, when we open manual merge tasks in IDD (Activevos), the tasks may take a very long time to open up and some of the tasks don't open up and return a blank screen. In those scenarios, follow the above infinispan settings to resolve the issue.

2) The infinispanConfig.xml file is available in two locations. 
          a) <<INFA_MDM>>/hub/server/resources and <<INFA_MDM>>/hub/server/resources  and 
          b) <<INFA_MDM>>/hub/cleanse/resources 

3) DATA_OBJECTS cache item is wrongly added twice in some of the MDM versions. You can remove one of the items.

Applies To
Product: MDM Multidomain
Problem Type: Configuration; Performance; Connectivity; Stability; Sizing
User Type: Administrator; Developer
Project Phase: Configure; Implement; Optimize
Product Version: MDM
Database:
Operating System:
Other Software:

Reference

Attachments

Last Modified Date:11/13/2019 9:15 AMID:509572
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)