Bug #103808 | group repl MY-013328: Certification information is too large for transmission | ||
---|---|---|---|
Submitted: | 26 May 2021 4:09 | Modified: | 30 Jun 2021 13:14 |
Reporter: | beon feng | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Group Replication | Severity: | S3 (Non-critical) |
Version: | 8.0.22 | OS: | CentOS (CentOS Linux release 7.8.2003 (Core)) |
Assigned to: | MySQL Verification Team | CPU Architecture: | x86 |
[26 May 2021 4:09]
beon feng
[27 May 2021 0:27]
MySQL Verification Team
Hi, This looks like duplicate of https://bugs.mysql.com/bug.php?id=99778 can you retry this with 8.0.25 Thanks Bogdan
[27 May 2021 5:53]
beon feng
ok, thanks for suggestion. I have read the bug-99778, and I have a question: The reason for bug-99778 is that the certification information is too big after cloneing procedure, which happens on group_replication_recovery . Then considering the common points of this two, is the cause of my bug-103880 poor disk capacity of the server during performance test?in other words, if flashback speed is slow or takes a long time, then "Certification information is too large for transmission." happens. whether group_replication_recovery or group_replication_applier ?
[27 May 2021 6:14]
MySQL Verification Team
Hi, It was happening when disk/network performance was not good or the database is too big anyhow, it happened when cloning took a considerable amount of time. This should be fixed in .22 and even more tuned in .25 that's why I asked if you can reproduce this with 8.0.25, as with 8.0.25 you should not have this problem anymore. If you can also reproduce it with 8.0.25 please let us know.
[27 May 2021 6:47]
beon feng
ok, thanks, I will retry that with 8.0.25.
[1 Jul 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".