MySQL 5.7複製報錯Client requested master to start replication from impossible
錯誤日誌中的資訊
2017-12-12T07:41:47.070228Z 57896 [ERROR] Error reading packet from server for channel 'master_4': Client requested master to start replication from impossible position; the first event 'mysql-bin.000003' at 31342251, the last event read from '/data/db_log/mysql-bin.000003' at 4, the last byte read from '/data/db_log/mysql-bin.000003' at 4. (server_errno=1236)
2017-12-12T07:41:47.077618Z 57896 [ERROR] Slave I/O for channel 'master_4': Got fatal error 1236 from master when reading data from binary log: 'Client requested master to start replication from impossible position; the first event 'mysql-bin.000003' at 31342251, the last event read from '/data/db_log/mysql-bin.000003' at 4, the last byte read from '/data/db_log/mysql-bin.000003' at 4.', Error_code: 1236
報錯原因
執行 change master 語句時，裡面的 master_log_file 寫的不正確
解決方法
在 change master 語句裡，寫上正確的 master_log_file
2017-12-12T07:41:47.070228Z 57896 [ERROR] Error reading packet from server for channel 'master_4': Client requested master to start replication from impossible position; the first event 'mysql-bin.000003' at 31342251, the last event read from '/data/db_log/mysql-bin.000003' at 4, the last byte read from '/data/db_log/mysql-bin.000003' at 4. (server_errno=1236)
2017-12-12T07:41:47.077618Z 57896 [ERROR] Slave I/O for channel 'master_4': Got fatal error 1236 from master when reading data from binary log: 'Client requested master to start replication from impossible position; the first event 'mysql-bin.000003' at 31342251, the last event read from '/data/db_log/mysql-bin.000003' at 4, the last byte read from '/data/db_log/mysql-bin.000003' at 4.', Error_code: 1236
報錯原因
執行 change master 語句時，裡面的 master_log_file 寫的不正確
解決方法
在 change master 語句裡，寫上正確的 master_log_file
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/26506993/viewspace-2148601/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- MySQL主從同步報Client requested master to start replication from positionMySql主從同步clientAST
- mysql replication複製錯誤(zt)MySql
- MySQL 5.7組複製(group replication)的要求和限制MySql
- MySQL主從複製報錯：Got fatal error 1236 from master when reading data fromMySqlGoErrorAST
- MySQL5.7半同步複製報錯案例分析MySql
- Mysql 5.7 基於組複製(MySQL Group Replication) - 運維小結MySql運維
- MySQL複製環境Slave報錯"Got fatal error 1236 from master when reading data"MySqlGoErrorAST
- Percona MySQL 5.6 主主複製環境報錯"Got fatal error 1236 from master.."MySqlGoErrorAST
- MySQL5.6 -> MySQL5.7 跨版本多源複製(Multi-Source Replication)MySql
- 理解 MySQL（3）：複製(Replication)MySql
- mysql replication /mysql 主從複製原理MySql
- MySQL 5.7 多主複製報錯Coordinator stopped because there were error(s)MySqlError
- mysql master-slave複製錯誤［解決事例］MySqlAST
- MySQL 5.7並行複製MySql並行
- mysql 5.7半同步複製MySql
- mysql 5.7多源複製MySql
- MySQL 5.7 並行複製MySql並行
- MySQL報錯Slave: received end packet from server, apparent master shutdownMySqlServerAPPAST
- 【MongoDB】主從複製(Master-Slave Replication)簡單實現MongoDBAST
- [Mysql]Mysql5.7並行複製MySql並行
- 【Mysql】mysql5.7無損複製MySql
- MySQL複製3--配置MasterMySqlAST
- mysql5.7主從複製，主主複製MySql
- MYSQL並行複製（parallel replication部署篇）MySql並行Parallel
- Mysql5.7半同步複製MySql
- MySQL 5.7搭建多源複製MySql
- MySQL 5.7 延遲複製配置MySql
- mysql複製報錯案例處理MySql
- MySQL5.7主從複製-半同步複製搭建MySql
- MySQL Replication的複製執行緒介紹MySql執行緒
- MySQL5.7主從複製教程MySql
- mysql 5.7開啟並行複製MySql並行
- 半同步複製報錯mysql8.0.25MySql
- 【Mysql】Mysql5.7的多源複製搭建MySql
- MySQL 5.7.17 組複製(group replication)的要求和限制MySql
- MySQL 5.7.9多源複製報錯修復MySql
- mysql 5.7 主從複製搭建及原理MySql
- MySQL 5.7 複製的過濾引數MySql