| Bug #38008 | invalid Relay_Log_Space value after slave i/o error | ||
|---|---|---|---|
| Submitted: | 10 Jul 2008 6:37 | Modified: | 9 Mar 2012 16:56 |
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.1.24 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Relay_Log_Space | ||
[10 Jul 2008 6:38]
MySQL Verification Team
error logs and some show slave status snapshots.
Attachment: bug38008_logs.txt (text/plain), 25.72 KiB.
[16 Jan 2009 17:03]
Susanne Ebrecht
Shane, please will you look if this also happens with actual 5.1 version?
[17 Feb 2009 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[19 Feb 2010 14:53]
Susanne Ebrecht
Sorry, bug number confusion ... bug #51194 is the duplicate and not the above one.
[29 Mar 2010 4:53]
Sveta Smirnova
Thank you for the report. Please provide output of DIR path/to/dir/where/relay/logs/located and relay.index file.
[29 Apr 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[9 Mar 2012 11:38]
MySQL Verification Team
i cant repeat this on 5.1.24 or 5.1.61 anymore. not sure how i did it to begin with.
[9 Mar 2012 16:56]
Sveta Smirnova
Thank you for the feedback. Closed as "Can't repeat" for now.
Description: after some slave i/o errors, show slave status outputs a negative longlong value for relay_log_space: mysql> show slave status\G *************************** 1. row *************************** Slave_IO_State: Reconnecting after a failed master event read Master_Host: 127.0.0.1 Master_User: root Master_Port: 3307 Connect_Retry: 60 Master_Log_File: xp64-bin.007566 Read_Master_Log_Pos: 4 Relay_Log_File: xp64-relay-bin.015121 Relay_Log_Pos: 148 Relay_Master_Log_File: xp64-bin.007566 Slave_IO_Running: No Slave_SQL_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 4 Relay_Log_Space: 18446744073709547643 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: NULL Master_SSL_Verify_Server_Cert: No Last_IO_Errno: 2003 Last_IO_Error: error reconnecting to master 'root@127.0.0.1:3307' Last_SQL_Errno: 0 Last_SQL_Error: according to the manual: " #Relay_Log_Space The total combined size of all existing relay logs. " How to repeat: setup replication and make some traffic. stop/start the master every 30 seconds. run show slave status on the slave until the error happens. i used max_binlog_size=4096 in my tests.