-rw-rw---- 1 mysql mysql 38G May 9 09:36 undo004
-rw-rw---- 1 mysql mysql 35G May 9 09:36 undo012
-rw-rw---- 1 mysql mysql 38G May 9 09:36 undo002
-rw-rw---- 1 mysql mysql 38G May 9 09:36 undo003
-rw-rw---- 1 mysql mysql 35G May 9 09:36 undo009
-rw-rw---- 1 mysql mysql 35G May 9 09:36 undo011
-rw-rw---- 1 mysql mysql 35G May 9 09:36 undo010
-rw-rw---- 1 mysql mysql 38G May 9 09:36 undo006
-rw-rw---- 1 mysql mysql 38G May 9 09:36 undo005
-rw-rw---- 1 mysql mysql 35G May 9 09:36 undo008
-rw-rw---- 1 mysql mysql 38G May 9 09:36 undo007
-rw-rw---- 1 mysql mysql 42G May 9 09:36 undo001
Do note that MYSQL 5.6 already reached EOL and is strongly suggested to upgrade to 5.7
I see that all the undo tablespaces were updated “around the same time”. Chances are there was a very large transaction ongoing, and the inability of MySQL purge threads to remove undo entries until the transaction finished, made the files grew so much.
Next time undo logs are needed, the existing files unused internal space will be used instead of growing the files again (unless you do a larger transacion that requires even more undo log entries).
Hello @Daljit1,
Upgrading to 5.7 from 5.6 is very simple. Stop 5.6. Install 5.7 packages (replace 5.6). Start 5.7. Very simple. Be sure to take a complete backup of the 5.6 data directory after you stop mysql. Just copy the directory somewhere safe.
Any reason behind that the undo size getting increasing.(mysql 5.6)
-rw-rw---- 1 mysql mysql 77G Sep 14 14:31 undo011
-rw-rw---- 1 mysql mysql 85G Sep 14 14:40 undo007
-rw-rw---- 1 mysql mysql 85G Sep 14 14:47 undo006
-rw-rw---- 1 mysql mysql 85G Sep 14 15:00 undo002
-rw-rw---- 1 mysql mysql 85G Sep 14 15:03 undo003
-rw-rw---- 1 mysql mysql 92G Sep 14 15:07 undo001
-rw-rw---- 1 mysql mysql 85G Sep 14 15:07 undo004
-rw-rw---- 1 mysql mysql 77G Sep 14 15:07 undo009
-rw-rw---- 1 mysql mysql 77G Sep 14 15:13 undo012
-rw-rw---- 1 mysql mysql 77G Sep 14 15:15 undo008
-rw-rw---- 1 mysql mysql 85G Sep 14 15:16 undo005
-rw-rw---- 1 mysql mysql 77G Sep 14 15:17 undo010