下面是我奴隶的身份。主日志文件位于"mysql-bin-changelog.278337“位置,而从日志文件位于"mysql-bin-changelog.278008”位置。如何跳过当前执行的"Relay_Master_Log_File“不指向其他日志文件?
mysql> show slave status\G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: kdm-eink-prod.cfewehpmjefz.us-east-1.rds.amazonaws.com
Master_User: rdsrepladmin
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin-changelog.278337
Read_Master_Log_Pos: 120
Relay_Log_File: relaylog.377536
Relay_Log_Pos: 1148
Relay_Master_Log_File: mysql-bin-changelog.278008
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table: mysql.plugin,mysql.rds_monitor,mysql.rds_sysinfo,mysql.rds_replication_status,mysql.rds_history,innodb_memcache.config_options,innodb_memcache.cache_policies
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 975
Relay_Log_Space: 354792434
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: 98230
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 1113717901
Master_UUID: ec0eef96-a6e9-11e2-bdf0-0015174ecc8e
Master_Info_File: mysql.slave_master_info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Sending data
Master_Retry_Count: 86400
Master_Bind:
Last_IO_Error_Timestamp:
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set:
Executed_Gtid_Set:
Auto_Position: 0
1 row in set (0.24 sec)
ERROR:
No query specified发布于 2016-04-15 19:22:38
复制滞后通常是通过查找以下内容之间的差异来衡量的
(Relay_Master_Log_File,Exec_Master_Log_Pos)(Master_Log_File,Read_Master_Log_Pos)从我在SHOW SLAVE STATUS\G上看到的
278337 - 278008)要在mysql-bin-changelog.278337之后处理。354792434 (338M)。如果Seconds_Behind_Master每秒钟稳步增长一次,您将不得不等待它,让复制赶上它。这是一个奇怪的指示,表明您正在运行一些可怕的查询,使得等待处理的二进制日志数量增加。您可以通过运行show processlist;来查看该查询,并查找具有与Seconds_Behind_Master相同编号的Time的SQL线程(其中用户为system user)。
如果你不能等待复制的追赶,你只需要旋转另一个只读的奴隶,并丢弃这个非常潜在的奴隶。
https://dba.stackexchange.com/questions/135412
复制相似问题