Bug #91933 | MySQL Group Replication - Transaction hangs in COMMIT state at primary | ||
---|---|---|---|
Submitted: | 8 Aug 2018 9:22 | Modified: | 11 Mar 2019 16:36 |
Reporter: | Yashwanth Aluru | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Group Replication | Severity: | S1 (Critical) |
Version: | 8.0.11 | OS: | CentOS |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[8 Aug 2018 9:22]
Yashwanth Aluru
[11 Feb 2019 16:36]
MySQL Verification Team
I can't say if this is a bug or not, but my first guess is that this is not a bug but a miss use of the system, and that you might need some support&consulting on how to break that flow rather then pushing large transaction trough GR. you have transaction_size_limit set https://dev.mysql.com/doc/refman/5.7/en/group-replication-options.html#sysvar_group_replic... how big is that transaction you are trying to push trough? Note that large transactions can take significant time and memory to execute. e.g. look at bug #84785 kind regards Bogdan
[12 Mar 2019 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".