Bug #110774 | 'show replica status' set the field_flag of 'Second_Behind_Source' NOTNULL | ||
---|---|---|---|
Submitted: | 23 Apr 2023 13:52 | Modified: | 25 Apr 2023 2:49 |
Reporter: | huigen yang | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 8.0.33 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[23 Apr 2023 13:52]
huigen yang
[24 Apr 2023 12:49]
MySQL Verification Team
Hi Mr. yang, Thank you for your bug report. Your code analysis is quite correct. However, it is intended behaviour that replica can not be NULL seconds behind master. Replica is always some seconds behind master, which is why NOT NULL is forced and some value is inserted. Let us know whether this is understandable.
[25 Apr 2023 2:49]
huigen yang
Dear MYSQL Team, Thanks for your reply. But Replica behind source is not always null indeed. Probably SQL thread or IO thread is not running,It may also be possible slave don't connect to the master.These situations may all lead to the value of Second_Behind_Source is NULL. Actually,I found the value of Second_Behind_Source is NULL when i executed ‘show replica status’ in a master. The same situation also occurs in SQL_Remaining_Delay.I find this description in your Official document: SQL_Remaining_Delay: When Replica_SQL_Running_State is Waiting until MASTER_DELAY seconds after master executed event, this field contains an integer indicating the number of seconds left of the delay. At other times, this field is NULL. #https://dev.mysql.com/doc/refman/8.0/en/replication-delayed.html Best Regards.