Managing MySQL Version Upgrades. Operating Systems. About the Author OTN TOUR years with MySQL / 26 years with RDBMS

Transcription

1 About the Author Ronald BRADFORD Managing MySQL Version Upgrades Ronald Bradford 16 years with MySQL / 26 years with RDBMS Senior Consultant at MySQL Inc (06-08) Consultant for Oracle Corporation (96-99) Published author of 4 MySQL books OTN TOUR 2015 Uruguay Argentina Chile Peru Latin America Oracle User Groups Community Operating Systems

2 Operating Systems MySQL versions In this presentation will only be discussing RHEL/OL/CentOS versions MySQL is also available on Ubuntu/Debian Windows Solaris Mac OS X FreeBSD SuSE... MySQL version history EOL , 4.0, 4.1, 5.0, 5.1 GA - 5.5, 5.6 DMR BEFORE Oracle v3.23 v v4.1 v MySQL (.com) Sun (.com) 2005 Innobase Oracle (.com)

3 v MySQL (.com) 2008 v5.1 v5.2 X DURING SUN X v6.0 4/21/2009 v5.4 beta X Sun (.com) 4/20/2009 Oracle (.com) Acquisition announcement Proven Scaling Our Delta /2009 1/2010 4/2009 v /10 v5.1 7/2010 v5.1 Sun (.com) 12/2010 v5.5 11/10 v5.2 4/2011 v5.5 2/12 V5.3 4/12 v5.5 3/2013 v5.6 10/13 v5.6 3/14 v10.0 Now July 2015 Oracle (.com) Percona Server Maria DB installation types Installation types for RHEL/OL Distro repo 3rd Party repo Webtatic, Remi Oracle repo tar.gz Source RHEL/OL Installation

4 RHEL/OL 6 default ISO Oracle Linux 6 default iso mysql-libs-5.1 package default install # Install MySQL cd /tmp wget yum localinstall -y mysql-community-releaseel6-5.noarch.rpm rm -f mysql-community-release-el6-5.noarch.rpm sudo yum-config-manager --disable mysql56-community sudo yum-config-manager --enable mysql55-community yum repolist enabled grep mysql yum install -y mysql-community-server rpm -qa grep mysql service mysqld start chkconfig mysqld on mysql -uroot -e "SELECT VERSION()" MySQL 5.5 default rpms Oracle yum repo $ rpm -qa grep mysql mysql-community-client el6.x86_64 mysql-community-common el6.x86_64 mysql-community-libs-compat el6.x86_64 mysql-community-libs el6.x86_64 mysql-community-server el6.x86_64 Minimum installed Additional packages exist Oracle yum repo supports MySQL 5.5 MySQL 5.6 MySQL 5.7 MySQL workbench/connectors/utilities

5 distro conflict RHEL/OL Distro mysql-server Oracle Distro mysql-community-server package names RHEL/OL Default $ yum info mysql-server Loaded plugins: security Available Packages Name : mysql-server Arch : x86_64 Version : Release : 5.el6_6 Size : 8.6 M Repo : public_ol6_latest Summary : The MySQL server and related files URL : License : GPLv2 with exceptions RHEL/OL 6 MySQL 5.1 EOL 2013 Description : MySQL is a multi-user, multi-threaded SQL database server. MySQL is a : client/server implementation consisting of a server daemon (mysqld) : and many different client programs and libraries. This package contains : the MySQL server and some accompanying files and directories. $ yum info mysql-community-server package names Oracle Repo Available Packages Name : mysql-community-server Arch : x86_64 Version : Release : 2.el6 Size : 53 M Repo : mysql56-community Summary : A very fast and reliable SQL database server URL : RHEL/OL Upgrade

6 default upgrade standard upgrade $ mysql -e "SELECT VERSION()" VERSION() $ sudo yum-config-manager --disable mysql55-community $ sudo yum-config-manager --enable mysql56-community $ sudo yum update mysql-community-server $ mysql -e "SELECT VERSION()" VERSION() This is not a completed upgrade yum update is not enough $ tail -20 /var/log/mysqld.log :28: [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure :28: [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure :28: [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure :28: [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure :28: [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure :28: [ERROR] Native table 'performance_schema'.'users' has the wrong structure :28: [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure :28: [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure :28: [ERROR] Native table 'performance_schema'.'socket_instances' has the error wrong log structure :28: [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure :28: [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has Always check the mysql_upgrade $ sudo mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck with default connection arguments Warning: Using a password on the command line interface can be insecure. Running 'mysqlcheck with default connection arguments Warning: Using a password on the command line interface can be insecure. mysql.columns_priv mysql.db mysql.event mysql.func mysql.general_log mysql.help_category mysql.help_keyword mysql.help_relation mysql.help_topic mysql.host mysql.ndb_binlog_index mysql.plugin mysql.proc mysql.procs_priv mysql.proxies_priv mysql.servers mysql.slow_log mysql.tables_priv mysql_upgrade must also be run on a running instance Repo Change

7 Legacy installation No Oracle yum repo before 5.5 No path from non-oracle repo to Oracle repo DB data structure is compatible Software removal and re-installation required Compatibility MySQL 5.5 to 5.6 reserved words Reserved Words Legacy TIMESTAMP usage FULLTEXT Indexes Client libraries Query Optimizer Clear text password warnings

8 reserved words reserved words mysql> SELECT VERSION(); version() mysql> CREATE TABLE mysql55(only CHAR(1)); Query, 0 rows affected (0.01 sec) mysql> INSERT INTO mysql55(only) VALUES('A'); Query, 1 row affected (0.00 sec) reserved words reserved words mysql> SELECT VERSION(); VERSION() mysql> CREATE TABLE mysql56(only CHAR(1)); mysql> CREATE TABLE table(c1 CHAR(1)); ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'table(c1 CHAR(1))' at line 1 mysql> CREATE TABLE `table`(c1 CHAR(1)); Query, 0 rows affected (0.01 sec) mysql> INSERT INTO mysql56(only) VALUES('A'); mysql> CREATE TABLE only(c1 CHAR(1)); Query, 0 rows affected (0.01 sec) Not all reserved words are affected in table strucutre mysql> INSERT INTO `table`(c1) VALUES('A'); Query, 1 row affected (0.01 sec) Reserved words can be used with backquotes (`)

9 timestamp defaults timestamp column $ tail /var/log/mysqld.log [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). TIMESTAMP datatype DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP fulltext optimizer MySQL 5.5 default storage engine changed to InnoDB CREATE TABLE without ENGINE=MyISAM fails in 5.5 MySQL 5.6 InnoDB now supports FTS Search results differ between MyISAM and InnoDB Some queries will have a different QEP Testing is necessary to validate if query is worse in performance Some queries are definitely better

10 clear text password $ mysql -uuser -ppassword Warning: Using a password on the command line interface can be insecure. mysql> CHANGE MASTER...; mysql> SHOW WARNINGS\G ************************** 1. row *************************** Level: Note Code: 1759 Message: Sending passwords in plain text without SSL/TLS is extremely insecure. *************************** 2. row *************************** Level: Note Code: 1760 Message: Storing MySQL user name or password information in the master.info repository is not secure and is therefore not recommended. Please see the MySQL Manual for more about this issue and possible alternatives. Configuration new configuration new defaults MySQL 5.6 Upgrade configuration path Inherit new configuration or keep legacy from prior version?

11 configuration configuration innodb_file_per_table 0 - Global tablespace (with multiple data files) 1 - Per table tablespace innodb_file_per_table Benefit Reclaim diskspace when deleting data Disadvantage Higher amount fsyncs

12 configuration configuration There is no only migration path to move tables to innodb_file_per_table=1 Must dump, drop, clear files, restart and reload all data to reset global tablespace Unprepared, you can be left with tables in old and new formats together performance_schema 5.5 default is OFF 5.6 default is ON Performance overhead Overhead is worth it for not well tuned systems configuration configuration innodb_log_file_size Generally increased for tuning systems Improvement helps in concurrency of untuned default system Restart required to implement new default (no additional work needed) max_connections 5.6 now supports more concurrent connections and more cores

13 sys Recommendations Install the sys schema in MySQL 5.6 Now included by default in MySQL upgrading Upgrading Options MySQL recommends upgrading to each version separately The also suggest to dump and load data This is impractical Can you upgrade from 5.0 to 5.5? It is [technically] possible, not recommended

14 replication replication MySQL replication is the easiest way to perform rolling upgrades A read replica can be a newer version Validates all writes (via binary log) Test reads via replay Do not use new replication configuration features until entire topology is upgraded. e.g. crash safe replication Issues with checksum in binary log conclusion Conclusion Moving from non Oracle yum repo is important first step Moving to 5.5 is the best base version A 3-6 month upgrade cadence is best MySQL replication is key for testing

15 Ronald Bradford