Bug #89954 | InnoDB cluster status inconsistent with group replication | ||
---|---|---|---|
Submitted: | 8 Mar 2018 6:01 | Modified: | 13 Apr 2018 3:09 |
Reporter: | Tony Wen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Group Replication | Severity: | S2 (Serious) |
Version: | mysql-community-server-minimal-5.7.20-1. | OS: | Oracle Linux (3.10.0-693.11.6.el7.x86_64) |
Assigned to: | CPU Architecture: | x86 |
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix>
- On windows use WinZip or a similar utility to split the large file
[9 Mar 2018 1:57]
Tony Wen
[9 Mar 2018 2:01]
Tony Wen
mysql logs of second similar failure
Attachment: t-baga1sh8sgc000ab24p0.log.tar (application/x-tar, text), 1.42 MiB.
[9 Mar 2018 9:17]
Tony Wen
log files of 2 mysql slave nodes
Attachment: tenant1.log.tar (application/x-tar, text), 58.00 KiB.