Troubleshoot Migration Issues

You may encounter some errors during migration. The following table helps you troubleshoot and resolve them.

Error Troubleshooting
Not enough disk space
  1. Increase the disk space that is allocated to ElasticSearch.
  2. Update the parameters in the application.yml file. See Migrate Events Service Data using Cluster Nodes or the Load Balancer.
Migration logs indicate a failure
  1. Analyse the logs of the particular index to identify the reason for the failure.
  2. Reinitiate the data migration. See Migrate Events Service Data using Cluster Nodes or the Load Balancer. The migration restarts from the last successful point.

Socket errors or server unavailable

 This occurs when the source or destination cluster is down. This can also happen if a node restarts during the migration process.

Ensure that the source and destination cluster is healthy, then reinitiate the migration steps.

migration_output_Final* metadata_migration_output*

This can happen because of runtime errors.

  1. Analyse the logs to identify the reason for the failure.
  2. If the issue is related to source or destination cluster health, ensure source and destination cluster is healthy.
  3. Reinitiate the data migration. See Migrate Events Service Data using Cluster Nodes or the Load Balancer. The migration restarts from the last successful point.
Destination cluster state is red due to node left before cutover
  1. Reset ElasticSearch Destination Cluster including data.
  2. Reset Migration.
  3. Reinitiate the data migration. See Migrate Events Service Data using Cluster Nodes or the Load Balancer.
Failed to parse mapping: can't merge a non object mapping This issue can occur when the migration utility tries to migrate the indexes that have dot fields. See Dot Field Errors During Migration.