I am having an issue with ibdata1 file having gotten very large (7 GB). Investigating the issue, I have a very large History:
TRANSACTIONS
------------
Trx id counter 53EEAD8B
Purge done for trx's n:o < 4E4CFA15 undo n:o < 0
History list length 9983250
And I assume it has to do with this:
Trx read view will not see trx with id >= 53EEAC64, sees < 4E4CF8F7
---TRANSACTION 4E4CF8F7, ACTIVE (PREPARED) 50164 sec recovered trx
, undo log entries 1
The seconds is low because of a recent mysql reboot that didn't purge it (the original time had it at about 26 days).
Soooo is this a transaction that I just need to get committed? If so, how is that done? Is it possible to determine what the transaction is?
TRANSACTIONS
------------
Trx id counter 53EEAD8B
Purge done for trx's n:o < 4E4CFA15 undo n:o < 0
History list length 9983250
And I assume it has to do with this:
Trx read view will not see trx with id >= 53EEAC64, sees < 4E4CF8F7
---TRANSACTION 4E4CF8F7, ACTIVE (PREPARED) 50164 sec recovered trx
, undo log entries 1
The seconds is low because of a recent mysql reboot that didn't purge it (the original time had it at about 26 days).
Soooo is this a transaction that I just need to get committed? If so, how is that done? Is it possible to determine what the transaction is?