Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have an extremely large db table (around 30GB data file), and I started optimizer on it with
mysqlcheck --optimize -A
Now, it’s already taken more than 2 hours, and I’m not sure when it’s going to finish. Would it result in data loss if I prematurely kill the job, because I want the table to be unlocked urgently?
In order to remove this from the “unanswered” list…
“Nope! It will NOT result in data loss if you prematurely kill the job, given your post facto confirmation that it did, indeed, not do so.”
That said, when MySQL optimizes a table, it creates a new table in the process. The downside is that you sometimes cannot optimize a large table when you belatedly realize that it’s consuming too much of the available hard disk space. The upside is that you can kill it prematurely without data loss.