Bug #114934 | In Heavy workload, it degenerates to use single thread replication in fact | ||
---|---|---|---|
Submitted: | 9 May 2024 7:33 | Modified: | 5 Jun 2024 2:06 |
Reporter: | Cai Minshen | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.7.44 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[9 May 2024 7:33]
Cai Minshen
[13 May 2024 23:51]
MySQL Verification Team
Hi, I was not able to reproduce this. Can you share more data, maybe create a script that will generate traffic that reproduces this. I made it as close as I can to your description and I was not able to recreate the problem.
[13 May 2024 23:52]
MySQL Verification Team
Another question - what version are you using. I'm testing with 8.4.0 LTS
[15 May 2024 12:14]
Cai Minshen
We use V5.7.44. We run 10 sysbench in parallel. Each one is target on a database. The sysbench command is like this: sysbench /usr/share/sysbench/oltp_read_write.lua --tables=2048 --table-size=2000000000 --mysql-user=<username> --mysql-db=<db_name>--mysql-host=<servername> --mysql_password='xxx' prepare
[15 May 2024 16:17]
MySQL Verification Team
Hi, As of October 25, 2023, MySQL 5.7 is covered under Oracle Sustaining Support. So there is no active development on 5.7 any more. Can you reproduce this with 8? I tried and I cannot. Those parallel sysbenchs all target their own database or they target all single database?
[5 Jun 2024 2:06]
Cai Minshen
We reproduce this issue on V8.0.36. Each sysbench is for its own database.