The Ultimate Guide to High Availability with MariaDB

Upgrade path from v1.0.9

Hi all,

I'm currently running MCS v1.0.9. What would be a better upgrade path:

(1) upgrade to MariaDB 10.5.4 with built in ColumnStore engine; even though it's in BETA

or

(2) upgrade to MCS 1.5.

Do I need to perform incremental upgrades from 1.0 -> 1.1 -> 1.2 -> 1.3 -> 1.4 -> 1.5 -> 10.5.4 should I choose any of the above options?

Additionally, is there a possibility of fallback in case the upgrade fails?

Thanks!

Answer Answered by Roman Nozdrin in this comment.

Greetings.

I might missed the point but we don't ship MCS with a forked MDB anymore. All future releases including 1.5 are shipped as MDB plugin.

Technically speaking you don't need incremental upgrades but you need to move your data manually though b/c all releases older 1.4 have their data under /usr/local/mariadb/columnstore/data whilst releases younger than 1.4 under /var/lib/columnstore. Save dbroot data, remove old packages, install new packages, stop MCS, copy in data, start MCS. This path doesn't allow S3 transition though. I belive there will be at least an 1.2 -> 1.5 upgrade doc available.

Starting with 1.5 community version plugin will install a single-node MCS. To have a multi-node cluster you need a separate package that controlls the cluster that is available for MariaDB customers only at least for now.

I don't think you can get 1.4 unless you are MariaDB customer I believe.

I suggest you to ask future questions in our google group.

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.