Bug #91830 | The GR master node inserts big data and cannot succeed for a long time | ||
---|---|---|---|
Submitted: | 30 Jul 2018 11:05 | Modified: | 22 Mar 2019 8:35 |
Reporter: | yghmgl yang | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | 5.7.23 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[30 Jul 2018 11:05]
yghmgl yang
[30 Jul 2018 11:40]
yghmgl yang
my config s1: [mysqld] port=3306 gtid_mode=ON enforce_gtid_consistency=ON max_allowed_packet=1073741824 master_info_repository=TABLE relay_log_info_repository=TABLE binlog_checksum=NONE log_slave_updates=ON log_bin=binlog binlog_format=ROW sync_binlog=1 binlog_order_commits=ON innodb_flush_log_at_trx_commit=1 slave_parallel_type=LOGICAL_CLOCK log-slave-updates=ON slave-preserve-commit-order=1 relay_log=relay-log slave_transaction_retries=10 transaction_write_set_extraction=XXHASH64 loose-group_replication_group_name="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa" loose-group_replication_start_on_boot=off loose-group_replication_ip_whitelist ='100.180.244.254,100.180.253.162,100.180.46.183' loose-group_replication_local_address="100.180.253.162:33060" loose-group_replication_group_seeds="100.180.253.162:33060,100.180.244.254:33060,100.180.46.183:33060" loose-group_replication_bootstrap_group=off s2: [mysqld] port=3307 gtid_mode=ON enforce_gtid_consistency=ON max_allowed_packet=1073741824 master_info_repository=TABLE relay_log_info_repository=TABLE binlog_checksum=NONE log_slave_updates=ON log_bin=binlog binlog_format=ROW sync_binlog=1 binlog_order_commits=ON innodb_flush_log_at_trx_commit=1 slave_parallel_type=LOGICAL_CLOCK log-slave-updates=ON slave-preserve-commit-order=1 relay_log=relay-log slave_transaction_retries=10 transaction_write_set_extraction=XXHASH64 loose-group_replication_group_name="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa" loose-group_replication_start_on_boot=off loose-group_replication_ip_whitelist ='100.180.244.254,100.180.253.162,100.180.46.183' loose-group_replication_local_address="100.180.244.254:33060" loose-group_replication_group_seeds="100.180.253.162:33060,100.180.244.254:33060,100.180.46.183:33060" loose-group_replication_bootstrap_group=off s3: [mysqld] port=3306 gtid_mode=ON enforce_gtid_consistency=ON max_allowed_packet=1073741824 master_info_repository=TABLE relay_log_info_repository=TABLE binlog_checksum=NONE log_slave_updates=ON log_bin=binlog binlog_format=ROW sync_binlog=1 binlog_order_commits=ON innodb_flush_log_at_trx_commit=1 slave_parallel_type=LOGICAL_CLOCK log-slave-updates=ON slave-preserve-commit-order=1 relay_log=relay-log slave_transaction_retries=10 transaction_write_set_extraction=XXHASH64 loose-group_replication_group_name="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa" loose-group_replication_start_on_boot=off loose-group_replication_ip_whitelist ='100.180.244.254,100.180.253.162,100.180.46.183' loose-group_replication_local_address="100.180.46.183:33060" loose-group_replication_group_seeds="100.180.253.162:33060,100.180.244.254:33060,100.180.46.183:33060" loose-group_replication_bootstrap_group=off
[8 Aug 2018 15:34]
MySQL Verification Team
Hi, I reproduced this but I'm torn between accepting this as a bug or deciding this is improperly sized platform for the use case you have, but since you already provided an idea how to fix the problem I'll accept this as a bug and let the dev team decide how to proceed forward. Thanks for the work you put into this, and for your report! kind regards Bogdan
[12 Aug 2018 11:00]
yghmgl yang
Hi, thanks for verified The current MIN_CACHED is set to 10, that is, the data is kept for up to 10 seconds in cach. If MIN_CACHED is set to a larger value, the bug may be fixed. Currently, the large transaction limit packet is 1 GB (more than 1 GB Will report an error while compression), so the value of MIN_CACHED can be as long as 1GB of data can be transmitted and can receive a response, of course, 1GB of transmission within MIN_CACHED seconds also requires bandwidth support.
[22 Mar 2019 8:35]
Margaret Fisher
Posted by developer: Fixed in MySQL 8.0.16 by WL #11610. Please see: https://dev.mysql.com/doc/refman/8.0/en/group-replication-performance-message-fragmentatio... https://dev.mysql.com/doc/refman/8.0/en/group-replication-communication-protocol.html https://dev.mysql.com/doc/refman/8.0/en/group-replication-options.html#sysvar_group_replic... https://dev.mysql.com/doc/refman/8.0/en/group-replication-functions-for-communication-prot...