Bug #113215 | mysqlslap response not returned | ||
---|---|---|---|
Submitted: | 25 Nov 2023 6:07 | Modified: | 10 Dec 1:11 |
Reporter: | 政実 白崎 | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 8.2 | OS: | Windows (11 22H2) |
Assigned to: | CPU Architecture: | Any |
[25 Nov 2023 6:07]
政実 白崎
[27 Nov 2023 10:42]
MySQL Verification Team
Hi, Thank you for your bug report. We have run the same command on our binary release of 8.2.0 and we have got the following output: Benchmark Average number of seconds to run all queries: 1.027 seconds Minimum number of seconds to run all queries: 1.027 seconds Maximum number of seconds to run all queries: 1.027 seconds Number of clients running queries: 1 Average number of queries per client: 1 Can't repeat.
[27 Nov 2023 11:19]
MySQL Verification Team
HI !!!! We have managed to reproduce this on Windows OS only. Hence, this is now a bug verified for 8.2.0, but ONLY for Windows OS platform.
[10 Dec 1:11]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Server 9.3.0 release, and here's the proposed changelog entry from the documentation team: The mysqlslap utility would stop being responsive if --auto-generate-sql-execute-number and --concurrency were specified without --auto-generate-sql or --query. Thank you for the bug report.
[10 Dec 10:50]
MySQL Verification Team
Thank you, Philip.
[10 Dec 23:52]
Philip Olson
Posted by developer: Release note updated, fixed in 9.2.0.
[11 Dec 10:35]
MySQL Verification Team
Great info, Philip !