Hello I have 26 legacy and standalone MariaDb 10.11.x servers which have an ibdata1 file larger than 10Gb. The largest is 276Gb (total DB's on that server are around 700G) and there's another 3 servers where it's over 100Gb. I track rate of growth, and some grow by over 1Gb/day, so a fair bit of our storage is given over to this problem.
Our newer servers have been built for some years with "innodb_undo_tablespaces=3" and that works brilliantly at keeping things sensible, but we've got a lot of legacy production servers. Half of these we're migrating from Rocky 8 to Debian 13, including a lift of mariadb 10.11 to 11.8 by means of moving the mysqldir vmdk from old to new, which is working well so far, but of course this just brings the problem over to the new host. I'm aware of the traditional fix, which is to do a full sqldump, wipe, add the above and restore. Unfortunately, many of our databases are well over a Tb now, with our largest being 11Tb. Dumping that and restoring it, even with fast storage, is an amount of downtime we just can't arrange. My response so far has been to kick the problem down the road and hope that one day, the clever people at MariaDb will somehow invent a method to automatically solve this without needing a dump/restore and affecting downtime. Am I being naively optimistic in thinking this is solvable and one day might be? Or has it already been solved and I just didn't get the memo? Simon Avery Linux Sysadmin: ATASS Sports Oxygen House | Grenadier Road, Exeter Business Park | EX1 3LH www.atass-sports.co.uk<http://www.atass-sports.co.uk/>
_______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
