Symptom
MySQL InnoDB restores with the file_per_table option can take a long time to terminate after a restore is complete.
Cause
After a restore of InnoDB file_per_table databases completes, the tasks will continue to display as running, while the MySQL temporary instance log info is dumped into the cdp.log file.
A large number of InnoDB tables using file_per_table can cause a significant delay in completing the task.
Resolution
Now, the MySQL restore will only dump the MySQL temporary instance log files to the CDP Server if the CDP Server is unable to start the MySQL temporary instance.