Version 3 by Nata Ramanenka
on May 07, 2012 02:45.
<< Changes from 2 to 3
compared with
Current by Shannon George
on May 08, 2012 12:42.
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (6)

View Page History
...
MySQL InnoDB restores with the {{file_per_table}} option can take a long time to terminate after a restore is complete.&nbsp;
{kb-cause}
When restoring InnoDB {{file_per_table databases}}, after the restore completes, the tasks will continue to show as running while the temp instance MySQL log info is dumped into the {{cdp.log}} file.
After a restore of InnoDB {{file_per_table databases}}&nbsp;completes, the tasks will continue to display as running, while the MySQL temporary&nbsp;instance&nbsp;log info is dumped into the {{cdp.log}} file.

When there are a large number of InnoDB tables using {{file_per_table}}, this can cause a significant delay in completing the task.
A large number of InnoDB tables using {{file_per_table}}&nbsp;can cause a significant delay in completing the task.

{kb-resolution}
The MySQL restore will only dump the MySQL temporary instance log files to the CDP Server now if the CDP Server is unable to start the temporary MySQL instance.
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&nbsp;instance.


...