So I've done some more digging on this.
1. Upgraded to MySQL 5.5.37
2. Made sure we didn't have any old/long running transactions--nothing
more than a few seconds.
3. Did a dump/reload in to a new DB and started with an empty history
list. A few days later, we're back up over 3mil
Hi Brad,
-Original Message-
From: Brad Heller [mailto:b...@cloudability.com]
Sent: Sunday, 7 September 2014 03:07
To: MySQL General List
Subject: MySQL 5.5.33 History list not purging?
For some reason, the history list isn't purging on one of my masters. This is
causing all kinds
Am 06.09.2014 um 19:07 schrieb Brad Heller:
For some reason, the history list isn't purging on one of my masters. This
is causing all kinds of weird issues/behavior with reads
so why do you not just try to update first?
5.5.39 is recent and contains *a lot* of bufixes
look at the changelogs -
Good point. We'll try that out.
I noticed our ibdata file is gigantic now, likely due to the alter table
migration we ran. What's the relationship here, do you think?
*Brad Heller *| Director of Engineering | Cloudability.com | 541-231-1514 |
Skype: brad.heller | @bradhe
