這期內容當中小編將會給大家帶來有關為什么MySQL 5.7主庫崩潰切備庫，文章內容豐富且以專業的角度為大家分析和敘述，閱讀完這篇文章希望大家可以有所收獲。

站在用戶的角度思考問題，與客戶深入溝通，找到豐寧網站設計與豐寧網站推廣的解決方案，憑借多年的經驗，讓設計與互聯網技術結合，創造個性化、用戶體驗好的作品，建站類型包括：成都網站設計、成都網站建設、企業官網、英文網站、手機端網站、網站推廣、域名注冊、網絡空間、企業郵箱。業務覆蓋豐寧地區。

場景：

MySQL主庫無故宕機：判斷是IO問題導致。

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

information that should help you find out what is causing the crash.

200118 02:11:39 mysqld_safe Number of processes running now: 0

200118 02:11:39 mysqld_safe mysqld restarted

原來主庫的my.cnf：

# For advice on how to change settings please see

# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html

# *** DO NOT EDIT THIS FILE. It's a template which will be copied to the

# *** default location during install, and will be replaced if you

# *** upgrade to a newer version of MySQL.

[mysqld]

# Remove leading # and set to the amount of RAM for the most important data

# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.

# innodb_buffer_pool_size = 128M

# Remove leading # to turn on a very important data integrity option: logging

# changes to the binary log between backups.

# log_bin

# These are commonly set, remove the # and set as required.

# basedir = .....

# datadir = .....

# port = .....

# server_id = .....

# socket = .....

basedir=/usr/local/mysql

datadir=/data/bak1

socket=/tmp/mysql.sock

server-id =11224722

default_password_lifetime=0

log-bin=/data/bak1/mysql-bin2

expire_logs_days = 1

max_binlog_size =600M

binlog_format = MIXED

#max_allowed_packet =1*1024*1024*1024

max_allowed_packet =1024M

event_scheduler = 1

transaction-isolation = READ-COMMITTED

max_connections=5000

innodb_buffer_pool_size = 80G

# Remove leading # to set options mainly useful for reporting servers.

# The server defaults are faster for transactions and fast SELECTs.

# Adjust sizes as needed, experiment to find the optimal values.

# join_buffer_size = 128M

# sort_buffer_size = 2M

# read_rnd_buffer_size = 2M 

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

1.確保所有的relay log全部更新完畢，在每個從庫上執行stop slave io_thread; show processlist;

直到看到Has read all relay log,則表示從庫更新都執行完畢了。

2.登陸所有從庫，查看master.info文件，對比選擇pos最大的作為新的主庫，這里我們選擇192.168.112.10為新的主庫。

3.登陸192.168.112.10，執行stop slave; 并進入數據庫目錄，刪除master.info和relay-log.info文件, 配置my.cnf文件，

開啟log-bin,如果有log-slaves-updates和read-only則要注釋掉，執行reset master。

新主庫的my.cnf：

[mysqld]

#datadir=/var/lib/mysql

#socket=/var/lib/mysql/mysql.sock

datadir=/data/db

socket=/tmp/mysql.sock

server-id =111210

log-bin = /data/db/mysql-bin.log

# binlog_format = MIXED

#relay-log = rep_relay_log1

#relay-log-index = rep_relay_log1

#log-error=/data/bak/mysqld1.err

#skip-slave-start = 1

default_password_lifetime=0

# binlog-ignore-db=mysql  

#expire_logs_days =7

max_connections = 2000

# user=mysql

# Disabling symbolic-links is recommended to prevent assorted security risks

#symbolic-links=0

max_allowed_packet =1024M

#master_info_repository=table

#relay_log_info_repository=table

#relay_log_recovery=1

#transaction-isolation = READ-COMMITTED

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

[mysqld_safe]

log-error=/var/log/mysqld.log

pid-file=/var/run/mysqld/mysqld.pid

4.SHOW MASTER STATUS; 查詢主庫狀態。

OK。

上述就是小編為大家分享的為什么MySQL 5.7主庫崩潰切備庫了，如果剛好有類似的疑惑，不妨參照上述分析進行理解。如果想知道更多相關知識，歡迎關注創新互聯行業資訊頻道。

標題名稱：為什么MySQL5.7主庫崩潰切備庫
文章來源：http://www.2m8n56k.cn/article46/jcgshg.html

成都網站建設公司_創新互聯，為您提供建站公司、服務器托管、網頁設計公司、定制開發、外貿建站、App設計

廣告

聲明：本網站發布的內容（圖片、視頻和文字）以用戶投稿、用戶轉載內容為主，如果涉及侵權請盡快告知，我們將會在第一時間刪除。文章觀點不代表本網站立場，如需處理請聯系客服。電話：028-86922220；郵箱：[email protected]。內容未經允許不得轉載，或轉載時需注明來源： 創新互聯