Bug #113891 | The value range of innodb_io_capacity_max is changed. | ||
---|---|---|---|
Submitted: | 5 Feb 3:23 | Modified: | 2 May 19:57 |
Reporter: | Zeng Zihao | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 8.0.36 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[5 Feb 3:23]
Zeng Zihao
[5 Feb 5:56]
MySQL Verification Team
Hello Zeng Zihao, Thank you for the report and feedback. Verified as described. regards, Umesh
[28 Feb 22:42]
Philip Olson
Posted by developer: Thank you Zeng Zihao, the documentation was updated to reflect the changes made in 8.0.29+ via that worklog.
[2 May 19:57]
Philip Olson
Posted by developer: The changes for this (and other) options is now fixed in the documentation source. The following InnoDB options were unified (max = 2**32-1) where 32/64-bit no longer differ as of 8.0.37/8.4.1: innodb_io_capacity, innodb_log_wait_for_flush_spin_hwm, and innodb_lru_scan_depth.