Upgrading from MariaDB 5.5 to MariaDB 10.0
You are viewing an old version of this article. View
the current version here.
What you need to know when upgrading from MariaDB 5.5 and MariaDB 10.0
As there has not been any changes in table or index formats between MariaDB 5.5 and MariaDB 10.0, the upgrade should be painless.
How to upgrade
- Shutdown and uninstall MariaDB 5.5
- Take a backup (this is the perfect time to take a backup of your databases)
- Install MariaDB 10.0.
- run mysql_upgrading (if your package is not doing that for you). This will do two things:
- Upgrade the permission tables in the mysql database with some new fields.
- Do a very quick check of all tables and mark them compatible with MariaDB 10.0
- Add new options to my.cnf to enable features.
- If you changed
my.cnf
then you need to restart mysqld.
- If you changed
Incompatible changes between 5.5 and 10.0
For most user, upgrading from 5.5 should be painless. Here follows a list of those things that has changed that could affect and upgrade:
Options that has changed default value
Most of the following options has increased a bit in value to give better performance. They should not use notable more memory, but some of them a bit more disk space.
Option | Old value | New value |
---|---|---|
aria-sort-buffer-size | 128M | 256M |
back_log | 50 | 150 |
innodb-buffer-pool-instances | 1 | 0 |
innodb-concurrency-tickets | 500 | 5000 |
innodb-log-file-size | 5M | 48M |
innodb-old-blocks-time | 0 | 1000 |
innodb-open-files | 300 | 0 |
innodb-purge-batch-size | 20 | 300 |
innodb-undo-logs ON | 20 | |
max-connect-errors | 10 | 100 |
max-relay-log-size | 0 | 1024M |
myisam-sort-buffer-size | 8M | 128M |
optimizer-switch | ... | Added extended_keys=on, exists_to_in=on |
Options that has been removed or renamed
The following options should be removed or renamed if you use them in your config files:
Option | Reason |
---|---|
engine-condition-pushdown Replaced with set optimizer_switch='engine_condition_pushdown=on' | |
innodb-adaptive-flushing-method | Removed by XtraDB |
innodb-autoextend-increment | Removed by XtraDB |
innodb-blocking-buffer-pool-restore | Removed by XtraDB |
innodb-buffer-pool-pages | Removed by XtraDB |
innodb-buffer-pool-pages-blob | Removed by XtraDB |
innodb-buffer-pool-pages-index | Removed by XtraDB |
innodb-buffer-pool-restore-at-startup | Removed by XtraDB |
innodb-buffer-pool-shm-checksum | Removed by XtraDB |
innodb-buffer-pool-shm-key | Removed by XtraDB |
innodb-checkpoint-age-target | Removed by XtraDB |
innodb-dict-size-limit | Removed by XtraDB |
innodb-doublewrite-file | Removed by XtraDB |
innodb-fast-checksum | Renamed to innodb-checksum-algorithm |
innodb-flush-neighbor-pages | Renamed to innodb-flush-neighbors |
innodb-ibuf-accel-rate | Removed by XtraDB |
innodb-ibuf-active-contract | Removed by XtraDB |
innodb-ibuf-max-size | Removed by XtraDB |
innodb-import-table-from-xtrabackup | Removed by XtraDB |
innodb-index-stats | Removed by XtraDB |
innodb-lazy-drop-table | Removed by XtraDB |
innodb-merge-sort-block-size | Removed by XtraDB |
innodb-persistent-stats-root-page | Removed by XtraDB |
innodb-read-ahead | Removed by XtraDB |
innodb-recovery-stats | Removed by XtraDB |
innodb-recovery-update-relay-log | Removed by XtraDB |
innodb-stats-auto-update | Renamed to innodb-stats-auto-recalc |
innodb-stats-update-need-lock | Removed by XtraDB |
innodb-sys-stats | Removed by XtraDB |
innodb-table-stats | Removed by XtraDB |
innodb-thread-concurrency-timer-based | Removed by XtraDB |
innodb-use-sys-stats-table | Removed by XtraDB |
xtradb-admin-command | Removed by XtraDB |
New major features you should consider using in MariaDB 10.0
For master / slave setups
- Global transaction id is enabled by default. This makes it easier to change a slave to a master.
- MariaDB 10.0 supports parallel slaves. You can enable this with slave-parallel-threads=#.
- Multi source replication
See also
Comments
Comments loading...
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.