MDM migration from 6.2.1 to 6.4.1 is slow

Talend Version 6.4.1

Summary

MDM migration from 6.2.1 to 6.4.1 is slow
Additional Versions  
Product Talend MDM
Component Migration
Problem Description Migration to 6.4.1 is taking considerable time.
Problem root cause amaltoOBJECTSCompletedRoutingOrderV2 and UpdateReport are taking the majority of the time for migration, as seen in the logs.
Solution or Workaround

To improve migration speed, perform the following:

  1. Disable Event Manager when migrating UpdateReport data.
  2. On the Target server:
    1. Stop the MDM service if running.
    2. Edit the mdm.conf file and set subscription.engine.autostart=false.
    3. Edit the log4j.xml file and add the following log category:
      <category name="com.amalto.core.server.routing">
       <priority value="FATAL" />
      </category>
    4. Restart the MDM server.
  3. To improve the performance for system containers, use the interactive mode to skip migration of unwanted system containers, like amaltoOBJECTSCompletedRoutingOrderV2.

For more information on migration methodology, see the two part series:

MDM Version Upgrade Methodology Part 1

MDM Version Upgrade Methodology Part 2

JIRA ticket number  
Version history
Revision #:
4 of 4
Last update:
‎09-29-2018 12:11 AM
Updated by:
 
Labels (3)