From MySQL+MMM to MariaDB+Galera Cluster: A High Availability Makeover
1–10 of 21 posts
Re: From MySQL+MMM to MariaDB+Galera Cluster: A High Availability Makeover
#2What I want to know is how people deal with innodb's dirty horrible secret - how ibdata can grow to infinite massive sizes and can never be reduced, ever. Regardless if you are using "file per table".
It is a ten year old bug [1] never addressed, no tools ever made to optimize it, and the larger your data, the sooner it will come to bite you. Doesn't matter if you are using mysql, percona or mariadb.
Re: From MySQL+MMM to MariaDB+Galera Cluster: A High Availability Makeover
#3What I want to know is how people deal with innodb's dirty horrible secret - how ibdata can grow to infinite massive sizes and can never be reduced, ever. Regardless if you are using "file per table". It is a ten year old bug [1] never addressed, no tools ever made to optimize it, and the larger your data, the sooner it will come to bite you. Doesn't matter if you are using mysql, percona or mariadb. [1] http://bugs.…
You want to "defrag" a live database? You're brave. Dump it and rebuild it - you should be able to do a node at a time.
Re: From MySQL+MMM to MariaDB+Galera Cluster: A High Availability Makeover
#4What I want to know is how people deal with innodb's dirty horrible secret - how ibdata can grow to infinite massive sizes and can never be reduced, ever. Regardless if you are using "file per table". It is a ten year old bug [1] never addressed, no tools ever made to optimize it, and the larger your data, the sooner it will come to bite you. Doesn't matter if you are using mysql, percona or mariadb. [1] http://bugs.…
You want to "defrag" a live database? You're brave. Dump it and rebuild it - you should be able to do a node at a time.
With terabyte sized databases, thousands of tables, not really an option to dump and reload.
Alter and optimize are already possible on a live innodb table, in theory it should not be exponentially harder to optimize ibdata.
Note that oracle solved this problem on their commercial database product.
Re: From MySQL+MMM to MariaDB+Galera Cluster: A High Availability Makeover
#5What I want to know is how people deal with innodb's dirty horrible secret - how ibdata can grow to infinite massive sizes and can never be reduced, ever. Regardless if you are using "file per table". It is a ten year old bug [1] never addressed, no tools ever made to optimize it, and the larger your data, the sooner it will come to bite you. Doesn't matter if you are using mysql, percona or mariadb. [1] http://bugs.…
The easiest way is to avoid running into the problem.
The main reason the central table space grows is due to rollback segments. To avoid collecting a lot of them there are two tips (in addition to file per table you mentioned):
1. Use multi-threaded purge. 2. Avoid very long running transactions (ie. 12+ hours)
Once we have done that, we don't really see this problem any longer.
Re: From MySQL+MMM to MariaDB+Galera Cluster: A High Availability Makeover
#6(shameless plug here)
Galera doesn't come out of the box with a secure SST option. SST, or state snapshot transfer, is how it bootstraps a new/failed node to get it close enough to continue with regular Galera replication. If you're running on a public cloud, you might care about secured SST communication. I wrote a drop-in secure rsync SST option, based on socat, that uses SSL encryption to seamlessly secure that traffic. Not perfect by any means, but it works without any futzing around.
Re: From MySQL+MMM to MariaDB+Galera Cluster: A High Availability Makeover
#7Why MariaDB+Galera vs. MySQL Cluster?
I read the political decision of Maria being more robust and non-Oracle, but was MySQL Cluster considered? And if not, why?
Re: From MySQL+MMM to MariaDB+Galera Cluster: A High Availability Makeover
#8Why MariaDB+Galera vs. MySQL Cluster? I read the political decision of Maria being more robust and non-Oracle, but was MySQL Cluster considered? And if not, why?
At that rate, I'm curious why Percona XtraDB Cluster (PXC) wasn't in the lineup of considerations.
Re: From MySQL+MMM to MariaDB+Galera Cluster: A High Availability Makeover
#9Why MariaDB+Galera vs. MySQL Cluster? I read the political decision of Maria being more robust and non-Oracle, but was MySQL Cluster considered? And if not, why?
At that rate, I'm curious why Percona XtraDB Cluster (PXC) wasn't in the lineup of considerations.
PXC and MariaDB+Galera are mostly the same code.
Re: From MySQL+MMM to MariaDB+Galera Cluster: A High Availability Makeover
#10What I want to know is how people deal with innodb's dirty horrible secret - how ibdata can grow to infinite massive sizes and can never be reduced, ever. Regardless if you are using "file per table". It is a ten year old bug [1] never addressed, no tools ever made to optimize it, and the larger your data, the sooner it will come to bite you. Doesn't matter if you are using mysql, percona or mariadb. [1] http://bugs.…
With a default my.cnf + innodb_file_per_table=1, ibdata0/ibdata1 will stay at 512M which isn't a big deal.