Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.6.14
-
None
-
RHEL 8
Description
I have a server where the history length keeps growing. At first we had them in shared system space but we moved them with using innodb_undo_tablespaces. This did not helped us either.
Right now the length is 124355327 and the server is not making transactions right now (for 1 hour) just to see if the purge starts. It's pretty idle.
Ihave the following parameters, most of them are extreme just to trigger some purge actions.
{{MariaDB [(none)]> show global variables like "innodb%purge%";
innodb_max_purge_lag | 50000 |
innodb_max_purge_lag_delay | 0 |
innodb_max_purge_lag_wait | 4294967295 |
innodb_purge_batch_size | 300 |
innodb_purge_rseg_truncate_frequency | 1 |
innodb_purge_threads | 32 |
innodb_undo_log_truncate | 1 |
innodb status:
Purge done for trx's n:o < 258032014 undo n:o < 5633661 state: running
|
History list length 124560317
|
Looks a little bit like #MDEV-29401 but that one should be fixed by the version we are already using.
Attachments
Issue Links
- relates to
-
MDEV-30628 10.6 performance regression with sustained high-connection write-only OLTP workload (55-80% degradation)
- Closed
-
MDEV-33213 History list is not shrunk unless there is a pause in the workload
- Closed