InnoDB Undo Log, MVCC Snapshots & Background Purge Threads

InnoDB's MVCC architecture storing historical row versions within Undo Tablespace rollback segments, reclaimed asynchronously by the background Purge thread.

Internal Architecture Breakdown

Under InnoDB MVCC, in-place index modifications generate historical rollback records in undo tablespaces. Read queries reconstruct point-in-time snapshots by traversing undo pointer chains backward.

The background Purge coordinator reclaims expired undo pages. If long-running transactions remain open, the History List Length (HLL) climbs precipitously, causing severe undo bloat and degraded query throughput.

Production Inspection Queries

MySQL

SHOW ENGINE INNODB STATUS\G; -- TRANSACTIONS: 'History list length'
SELECT * FROM information_schema.innodb_trx WHERE trx_started < NOW() - INTERVAL 1 HOUR;

Back to Glossary