Bug #107884 | Error message after stop semi sync replication | ||
---|---|---|---|
Submitted: | 14 Jul 2022 17:16 | Modified: | 16 Aug 2022 22:09 |
Reporter: | Roberto de Bem | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 8.0.29 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
Tags: | regression, semisynchronous replication |
[14 Jul 2022 17:16]
Roberto de Bem
[15 Jul 2022 15:15]
Roberto de Bem
The bug doesn't happen on version 8.0.26.
[16 Jul 2022 22:09]
MySQL Verification Team
Hi, Do you have another active replica running or you start with only one replica and you stop it? I'm not sure why would this be considered a bug, if it is true there are no active replicas to send data to? Can you please clarify?
[25 Jul 2022 18:36]
Scott Nemes
I reported the bug to Percona. Yes, there is one primary and two replicas in this situation. Stopping replication on one of the replicas causes this error in the primary logs. Second replica is still there, so should be no issue and no reason to have an "ERROR" in the logs. Was no error in 8.0.26, only started after upgrading to 8.0.28.
[26 Jul 2022 2:02]
MySQL Verification Team
Hi, having issues reproducing this. Can you upload full config from all three nodes? Is this bare metal or VM? Are you running this on-prem or in some cloud (we had some unexplained behaviors on azure)? Thanks
[26 Jul 2022 4:09]
Scott Nemes
Attached are the primary and replica configs for reference. Databases are running on-prem, VMs on dedicated hardware. The primary and replica VMs are all on different physical hosts.
[17 Aug 2022 1: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".