Upgrade MySQL5.1 to MySQL5.5 practical notes

Source: Internet
Author: User
In the past, most of the company's projects were on version 5.5, and there was just a project (free trading platform) with a small amount of data. A single server ran stably online and rarely took over,

In the past, most of the company's projects were on version 5.5, and there was just a project (free trading platform) with a small amount of data. A single server ran stably online and rarely took over,

In the past, most of the company's projects were on version 5.5, and there was just a project (free trading platform) with a small amount of data. A single server ran stably online and rarely took over, in order to unify the version, I plan to upgrade to MySQL 5.5... with the assistance of Mr. He, the upgrade was completed .. the following are some important parameters for the specific upgrade process and two major versions!

1. Changes to parameters in the my. cnf configuration file
# Skip-locking is not recognized in 5.5. It is changed to skip-external-locking.
# Log-long-format is not recognized in 5.5 and changed to log-short-format.
# Log_slow_queries is not recognized in 5.5 and changed to slow-query-log.
# Default-character-set = utf8 is not recognized in 5.5, and changed to character-set-server = utf8


# Comment out default_table_type = MyISAM, which is not recognized in 5.5
# Comment out myisam_max_extra_sort_file_size which is not recognized in 5.5


# Innodb_file_io_threads is not recognized and changed
Innodb_read_io_threads = 8
Innodb_write_io_threads = 8

# Increase the volume of dirty pages refreshed and the number of merged inserts to improve the disk I/O processing capability and adjust the disk IOPS capability

Innodb_io_capacity = 2000


# Change the previously built-in file format Antelope to Barracuda
Innodb_file_format = Barracuda


# Modify the dirty page from 25 to 90. The value can be selected between 70 and 90.
Innodb_max_dirty_pages_pct = 90


# Change the redo log of transaction logs from 256M to 1024 M
Innodb_log_file_size = 1024


# Using independent tablespace
Innodb_file_per_table = 1


Restart MySQL to take effect:
[Root @ db_fb05 mysql-5.1.62] # service mysqld restart
Shutting down MySQL. SUCCESS!
Starting MySQL... SUCCESS!
[Root @ db_fb05 mysql-5.1.62] #

Recommended reading:

MySQL 5.5 Command Line Client SQL common statements

Load Nginx in Ubuntu for high-performance WEB Server 5 --- MySQL master/Master Synchronization

Production Environment MySQL master/Master synchronization primary key conflict handling

MySQL Master/Slave failure error Got fatal error 1236

MySQL master-slave replication, implemented on a single server

Compile and install MySQL dual-instance in Ubuntu and configure master-slave Replication

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.