MySQL Forums
Forum List  »  InnoDB

Undo logs Bloat
Posted by: Azar Md
Date: November 11, 2025 03:48AM

we are experiencing a huge undo log bloat in the mysql version 8.0.40

size of the undo log files grown

580G temp_undo_003.ibu
102G temp_undo_004.ibu
521G undo_001
575G undo_002


History list length 2249562972


mysql> SELECT SPACE, NAME, STATE, FILE_SIZE, ALLOCATED_SIZE FROM information_schema.innodb_tablespaces WHERE SPACE_TYPE='Undo';
+------------+-----------------+----------+--------------+----------------+
| SPACE | NAME | STATE | FILE_SIZE | ALLOCATED_SIZE |
+------------+-----------------+----------+--------------+----------------+
| 4294966771 | innodb_undo_001 | active | 555879497728 | 555879653376 |
| 4294966897 | innodb_undo_002 | inactive | 616831123456 | 616831246336 |
| 4294967277 | temp_undo_003 | active | 618643062784 | 618643353600 |
| 4294967276 | temp_undo_004 | inactive | 109270007808 | 109270110208 |
+------------+-----------------+----------+--------------+----------------+
4 rows in set (0.06 sec)

I could confirm that there is no long running transaction, but it is a heavy write system where more upsert queries will be running.

it was about more than 30 days, it has been made inactive but still not become empty state.

Any best solution to overcome this issue of clearing all the space occupied by the undo logs, within a very short interval of time.

Options: ReplyQuote


Subject
Views
Written By
Posted
Undo logs Bloat
232
November 11, 2025 03:48AM


Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.