MariaDB MariaDB 10.1 is stable GA

With the release of 10.1.8, MariaDB takes a next step. MariaDB 10.1 is now considered a stable release.

MariaDB 10.1 has a couple of main themes:

• Security
• High Availability
• Scalability

During the last few years there have been many request for more security features in MariaDB. Actually it’s a trend in general. Since open source software is getting more attractive all the time, more functionality is wanted in areas where proprietary software typically has been leading. This is especially true for databases. In addition data privacy is a very hot topic.

The big new thing in security for MariaDB 10.1 is a complete data at rest encryption solution. The encryption that now is in use originates from Google’s encryption patch. It has now been migrated into MariaDB 10.1. The solution is fairly advanced, encrypting the actual data files on disk of course, but also all other places where data touches disk like the binlog in replication. It also introduces the concept of rolling encryption keys, where keys can be set to expire at some certain intervals causing data to be re-encrypted with new keys and becoming inaccessible with the old keys.

In addition to encryption, 10.1 also includes other security aspects like password validation with which one can define a scheme, for example with the popular cracklib library, against which new passwords are validated.

On the High Availability front there is a significant change. In 5.5 and 10.0 there are separate versions of MariaDB and MariaDB Galera Cluster. In 10.1 this has changed. There is only one MariaDB 10.1. It includes the cluster capabilities and they can just be switched on whenever needed.

In regards of scalability there are multiple aspects. On one hand the parallel slave replication introduced in MariaDB 10.0 is now further improved into what is called optimistic parallel replication. Very much simplified, this means that any INSERT/UPDATE/DELETE can be applied in parallel on the slave (even it wasn’t on the master) which in most cases will result in a performance gain.

When it comes to replication there is another very important compatibility aspect added to 10.1. MariaDB can now be a slave to MySQL 5.6 (or greater) also when MySQL 5.6 is configured to use GTID. This has been a highly voted feature request since users wants to be able to test MariaDB as part of their MySQL deployment. When migrating to MariaDB this functionality is also essential.

Another important aspect of scalability is that 10.1 includes a lot of performance improvements to perform better on CPUs with more processing power and more cores. Also on the disk IO side there are several improvements like page compression and defragmentation. Defragmentation is based on the patch developed first by Facebook and then further developed by Kakao Corp.

There are a lot of other new capabilities and improvements in MariaDB 10.1, like supporting new spatial reference systems and outputting explains in JSON. To get a complete list of new functionality please refer to the “What is MariaDB 10.1?” page.

Most important of all, go download MariaDB 10.1.8, install it, and start putting your workloads on it. Stay in contact with us by filing any findings that you think are wrong in Jira. You can also reach the developers of MariaDB on the #maria channel on Freenode IRC or email the developers by joining the mailing list maria-developers. Do enjoy!

Continue reading...

 

yay very good news... Centmin Mod 123.09beta01 has submenu option for MariaDB 10.0.x to 10.1.x upgrade as outlined at MariaDB - MariaDB 10.1.7 now available - upgrade for Centmin Mod LEMP stack | Centmin Mod Community However, still needs testing and feedback from folks

I'd probably wait for 4-6 further releases from MariaDB 10.1.x before officially using it as default for 123.09beta01 and higher releases

very interesting, I use parallel replication so will definitely try optimistic parallel replication

MariaDB page compression and defragmentation also look interesting

 

from Centmin Mod 123.09beta01

Code:

--------------------------------------------------------
Centmin Mod 1.2.3-eva2000.09 - http://centminmod.com
--------------------------------------------------------
                   Centmin Mod Menu                
--------------------------------------------------------
1).  Centmin Install
2).  Add Nginx vhost domain
3).  NSD setup domain name DNS
4).  Nginx Upgrade / Downgrade
5).  PHP Upgrade / Downgrade
6).  XCache Re-install
7).  APC Cache Re-install
8).  XCache Install
9).  APC Cache Install
10). Memcached Server Re-install
11). MariaDB 5.2/5.5 & 10.x Upgrade Sub-Menu
12). Zend OpCache Install/Re-install
13). Install ioping.sh vbtechsupport.com/1239/
14). SELinux disable
15). Install/Reinstall ImagicK PHP Extension
16). Change SSHD Port Number
17). Multi-thread compression: pigz,pbzip2,lbzip2...
18). Suhosin PHP Extension install
19). Install FFMPEG and FFMPEG PHP Extension
20). NSD Re-install
21). Update - Nginx + PHP-FPM + Siege
22). Add Wordpress Nginx vhost + WP Super Cache
23). Update Centmin Mod Code Base
24). Exit
--------------------------------------------------------
Enter option [ 1 - 24 ] 11
--------------------------------------------------------

Code:

--------------------------------------------------------
        MariaDB MySQL Upgrade Sub-Menu           
--------------------------------------------------------
1). MariaDB 5.2.x Branch Upgrade Only
2). MariaDB 5.2.x to MariaDB 5.5 YUM upgrade
3). MariaDB 5.5 to MariaDB 10.x YUM upgrade
4). MariaDB 5.5 to MariaDB 10.1.x YUM upgrade
5). MariaDB 10.x to MariaDB 10.1.x YUM upgrade
6). Back to Main menu
--------------------------------------------------------
Enter option [ 1 - 6 ] 5
--------------------------------------------------------

Code:

--------------------------------------------------------------------------------
This script's MariaDB 10.1.x upgrade process is still in beta testing stages.
So please test on a test server and not a live production server. But if you use
on live server or if MySQL databases already exist, please back them up before
running this upgrade script via mysqldump - instructions at:
http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html.

###############################################################
###        IMPORTANT MYSQLDUMP BACKUP BEFORE UPGRADE        ###
###      OR RISK DATA LOSS DUE TO MARIADB 10.1 Changes      ###
###############################################################

For each DATABASENAME backup via mysqldump i.e.

  mysqldump --opt --routines DATABASENAME > /path/to/DATABASENAME_backup.sql
--------------------------------------------------------------------------------

Have you backed up your databases ? [y/n] y

MariaDB 10.1.x no longer works with mydumper
MySQL backup tool. But still works with MariaDB 5.2.x
Do you want to continue with upgrade to MariaDB 10.1.x ? [y/n] y

Code:

*************************************************
MariaDB 10.1.x Repo setup...
*************************************************

Loaded plugins: fastestmirror, priorities
Cleaning repos: base epel extras mariadb rpmforge updates
Cleaning up everything
Cleaning up list of fastest mirrors
rpm --import http://yum.mariadb.org/RPM-GPG-KEY-MariaDB

*************************************************
MariaDB 10.1.x check available packages
yum -q list MariaDB-client MariaDB-common MariaDB-compat MariaDB-devel MariaDB-server MariaDB-shared
*************************************************

Installed Packages
MariaDB-client.x86_64               10.0.21-1.el7.centos                @mariadb
MariaDB-common.x86_64               10.0.21-1.el7.centos                @mariadb
MariaDB-compat.x86_64               10.0.21-1.el7.centos                @mariadb
MariaDB-devel.x86_64                10.0.21-1.el7.centos                @mariadb
MariaDB-shared.x86_64               10.0.21-1.el7.centos                @mariadb
Available Packages
MariaDB-client.x86_64               10.1.8-1.el7.centos                 mariadb
MariaDB-common.x86_64               10.1.8-1.el7.centos                 mariadb
MariaDB-compat.x86_64               10.1.8-1.el7.centos                 mariadb
MariaDB-devel.x86_64                10.1.8-1.el7.centos                 mariadb
MariaDB-server.x86_64               10.1.8-1.el7.centos                 mariadb
MariaDB-shared.x86_64               10.1.8-1.el7.centos                 mariadb
mariadb-devel.x86_64                1:5.5.44-1.el7_1                    updates
mariadb-server.x86_64               1:5.5.44-1.el7_1                    updates 

Code:

*************************************************
MariaDB 10.1.x YUM install...
yum -q -y install MariaDB-client MariaDB-common MariaDB-compat MariaDB-devel MariaDB-server MariaDB-shared
*************************************************

Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* base: mirrors.linode.com
* epel: mirror.smartmedia.net.id
* extras: mirrors.linode.com
* rpmforge: mirror.smartmedia.net.id
* updates: mirrors.linode.com
153 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package MariaDB-client.x86_64 0:10.0.21-1.el7.centos will be updated
---> Package MariaDB-client.x86_64 0:10.1.8-1.el7.centos will be an update
---> Package MariaDB-common.x86_64 0:10.0.21-1.el7.centos will be updated
---> Package MariaDB-common.x86_64 0:10.1.8-1.el7.centos will be an update
---> Package MariaDB-compat.x86_64 0:10.0.21-1.el7.centos will be updated
---> Package MariaDB-compat.x86_64 0:10.1.8-1.el7.centos will be an update
---> Package MariaDB-devel.x86_64 0:10.0.21-1.el7.centos will be updated
---> Package MariaDB-devel.x86_64 0:10.1.8-1.el7.centos will be an update
---> Package MariaDB-server.x86_64 0:10.1.8-1.el7.centos will be installed
---> Package MariaDB-shared.x86_64 0:10.0.21-1.el7.centos will be updated
---> Package MariaDB-shared.x86_64 0:10.1.8-1.el7.centos will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
Package             Arch        Version                     Repository    Size
================================================================================
Installing:
MariaDB-server      x86_64      10.1.8-1.el7.centos         mariadb       98 M
Updating:
MariaDB-client      x86_64      10.1.8-1.el7.centos         mariadb       38 M
MariaDB-common      x86_64      10.1.8-1.el7.centos         mariadb       43 k
MariaDB-compat      x86_64      10.1.8-1.el7.centos         mariadb      1.4 M
MariaDB-devel       x86_64      10.1.8-1.el7.centos         mariadb      6.5 M
MariaDB-shared      x86_64      10.1.8-1.el7.centos         mariadb      1.3 M

Transaction Summary
================================================================================
Install  1 Package
Upgrade  5 Packages

Total download size: 146 M

Code:

mysqladmin ver
mysqladmin  Ver 9.1 Distrib 10.1.8-MariaDB, for Linux on x86_64
Copyright (c) 2000, 2015, Oracle, MariaDB Corporation Ab and others.

Server version          10.1.8-MariaDB
Protocol version        10
Connection              Localhost via UNIX socket
UNIX socket             /var/lib/mysql/mysql.sock
Uptime:                 1 min 56 sec

Threads: 1  Questions: 1  Slow queries: 0  Opens: 0  Flush tables: 1  Open tables: 11  Queries per second avg: 0.008

 

MariaDB 10.1 can do 1 million queries per second « The MariaDB Blog

 

those sysbench benchmarks for MariaDB 10.1 remind me it's been a while since I've benchmarked Mysql with sysbench .. should dust off my tools

 

depends entirely on server hardware setup and configuration and MySQL 5.7 technically is faster and more improved for innodb that MySQL 5.6 and MariaDB 10.0.x and MariaDB 10.1.x does port some MySQL 5.7 stuff but only time will tell

that was specific for Power8 hardware i think what they claim

Looks like for CentOS 7 + chkconfig MariaDB 10.1.8 changed the service name from mysql to mariadb !

Code:

chkconfig mysql on
Note: Forwarding request to 'systemctl enable mysql.service'.
Failed to issue method call: No such file or directory

Code:

[root@centos7 ~]# chkconfig mariadb on
Note: Forwarding request to 'systemctl enable mariadb.service'.

but service restart works for mysql

Code:

[root@centos7 ~]# service mysql restart
Restarting mysql (via systemctl):                          [  OK  ]

[root@centos7 ~]# mysqlrestart
Restarting mysql (via systemctl):                          [  OK  ]

and new mariadb service name

Code:

[root@centos7 ~]# service mariadb restart
Redirecting to /bin/systemctl restart  mariadb.service

 

i added one for upgrade to 10.1.8 process it's only one needed.. rest is end user has to remember when they do stuff manually themselves

 

MariaDB 10.1 and MySQL 5.7 performance on commodity hardware « The MariaDB Blog

 

benchmarking can become an addiction if you let it

just some test runs for my sysbench script - it auto generates all the charts, tabulated data stats and spits out the test parameters used too so I don't have to do any manual leg work

 

Some folks reported crashes in MariaDB 10.0.x to 10.1.8 update so I'd wait longer for production live site usage. Centmin Mod will wait at least 4-6 releases later before becoming official.

MariaDB 10.1.9 bug fixed list so far ordered in descending priority list Issue Navigator - JIRA

 

I'm not going to use 10.1 until at least 3-4 releases after GA, so 10.1.13 is probably when I'd even look at using in production. Test fine but for production, I'll wait to see the ironing out of bugs from their official Jira bug tracker

 

nice.. i'm just being cautious - doesn't help if i monitor MariaDB jira bug tracker like a hawk hehe

FYI, MariaDB 10.1.10 fixed and outstanding bugs list Issue Navigator - JIRA

some of note for fixes due in MariaDB 10.1.10 which is due for release Dec 23rd, 2015

• [MDEV-8571] After mysqloptimize sometimes one of the tables is marked as crashed - JIRA
• [MDEV-8825] mysql_upgrade leaks the admin password when it spawns a shell process to execute mysqlcheck - JIRA
• [MDEV-9001] [PATCH] Fix DB name quoting in mysqldump --routine - JIRA
• [MDEV-8313] Got an error writing communication packets - JIRA
• [MDEV-7215] EXPLAIN REPLACE produces an error: Column count doesn't match value count - JIRA
• [MDEV-8295] CVE-2015-3210 PCRE vulnerability - JIRA
• [MDEV-8297] information_schema.innodb_sys_tablestats.modified_counter doesn't change on UPDATE - JIRA
• [MDEV-9147] Character set is ignored in Dynamic Column for saved string - JIRA
• [MDEV-9088] Server crashes on shutdown after the second post of feedback report - JIRA
• [MDEV-9227] Both CentOS service names mysql and mariadb exist ? - JIRA <-- mine and of note Systemd - MariaDB Knowledge Base
• [MDEV-8178] Wrong progress report for operations on InnoDB tables - JIRA
• [MDEV-9129] Server is restarting in the loop after crash - JIRA
• [MDEV-7588] [PATCH] Slow connections with thread pool and replication - JIRA