Bug #102548 semi-sync replication with ogg
| Submitted: | 10 Feb 2021 2:59 | Modified: | 3 Apr 2021 5:09 |
|---|---|---|---|
| Reporter: | HULONG CUI | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 5.7.22 | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | semi-sync | ||
[10 Feb 2021 2:59]
HULONG CUI
[10 Feb 2021 13:53]
MySQL Verification Team
Hi, Thanks for the report. Can you reproduce this with 5.7.33 ? kind regards Bogdan
[3 Mar 2021 4:49]
HULONG CUI
Because this is readl user environment cannot be upgraded。 Is there another way check or to identify the problem
[3 Mar 2021 5:09]
MySQL Verification Team
Hi, > environment cannot be upgraded The fix cannot be applied without an upgrade so if the environment can't be upgraded you for sure can't fix it. I cannot reproduce this issue with the modern version of MySQL Server and there are a number of changes in the semi-sync replication since your version, so unless you can reproduce this with the latest version there's nothing I can do.
[4 Apr 2021 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".
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.058 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.