Cloudera Docs

Scan stays in IN_PROGRESS indefinitely

When a scan never completes, cancel it from command history and retry. If cancel fails, see stuck-command troubleshooting.

Cause: The CMA Agent lost connection to the CMA Master during the scan, or the scan process on the agent was killed.

  1. Cancel the scan from command history (click the history icon on the cluster page).
  2. Retry the scan.
  3. If cancel does not work, see Scan or migration commands stuck in IN_PROGRESS state.