Cloudera Docs

Execution step stays in IN_PROGRESS

When a migration execution step remains in IN_PROGRESS, check the CMA Agent log for the underlying operation status before canceling and re-running.

Cause: The CMA Agent executing the step lost connectivity to the CMA Master, or the underlying operation (for example DistCp or a Cloudera Replication Manager policy) is still running.

  1. Check the CMA Agent log for the current step status.

    Default log path: /var/log/cma-agent/cma-agent-server.log

  2. If the underlying operation completed but status was not reported back, cancel the execution and create a new one.