Bug #89208 innodb.innodb_file_limit_check depends on OS open files limit
Submitted: 12 Jan 2018 13:36 Modified: 12 Jan 2018 14:50
Reporter: Alexey Kopytov Email Updates:
Status: Verified Impact on me:
Category:Tests: Engine Severity:S3 (Non-critical)
Version:5.7, 8.0 OS:Any
Assigned to: CPU Architecture:Any

[12 Jan 2018 13:36] Alexey Kopytov
The innodb.innodb_file_limit_check is based on the assumption that
setting "innodb_open_files=1000000" will trigger the following warning
in the error log:

  innodb_open_files should not be greater than the open_files_limit.

However, open_files_limit is auto-adjusted to the operating system limit
on the number of open files (ulimit -n). Which means if that limit is
higher than 1000000, the test fails.

How to repeat:
ulimit -n 1048576
./mtr innodb.innodb_file_limit_check
[12 Jan 2018 14:50] MySQL Verification Team
Thank you for the bug report.
[31 May 2018 8:18] Vasil Dimov
A simple fix to this would be to set open_files_limit to a lower value than 1000000 at the very beginning of the test, so that the attempt to set the InnoDB variable would deterministically fail.