Bug #94634 Out-of-order redo log file creation status reporting
Submitted: 12 Mar 2019 8:42 Modified: 31 Jan 2020 21:10
Reporter: Krunal Bauskar Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:8.0.15 OS:Any
Assigned to: CPU Architecture:Any

[12 Mar 2019 8:42] Krunal Bauskar
Recent changes done by mysql to buffer boot up message till log module is not initialized result in out-of-order messages about redo log creation.

First 2 lines below represent the progress of redo log creation. There is absolutely no hint as to what they are and they are appearing to be out-of-order from other redo log messages emitted below.


 100 200 300 400 500
 100 200 300 400 500
2019-03-12T08:34:21.066079Z 0 [Warning] [MY-010139] [Server] Changed limits: max_open_files: 1024 (requested 8161)
2019-03-12T08:34:21.066090Z 0 [Warning] [MY-010142] [Server] Changed limits: table_open_cache: 431 (requested 4000)
2019-03-12T08:34:21.261146Z 0 [Warning] [MY-010097] [Server] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2019-03-12T08:34:21.261162Z 0 [Note] [MY-010949] [Server] Basedir set to /opt/projects/percona/non-forked-oracle/binaries/mysql-8.0.15-linux-glibc2.12-x86_64/.
2019-03-12T08:34:21.261169Z 0 [System] [MY-010116] [Server] /opt/projects/percona/non-forked-oracle/binaries/mysql-8.0.15-linux-glibc2.12-x86_64/bin/mysqld (mysqld 8.0.15) starting as process 6246

How to repeat:
Start server with following params (besides standard params)

[12 Mar 2019 9:07] MySQL Verification Team
Hello Krunal,

Thank you for the report.
Verified as described.

[31 Jan 2020 21:10] Daniel Price
Posted by developer:
Fixed as of the upcoming 8.0.20 release, and here's the proposed changelog entry from the documentation team:

Additional information about InnoDB file writes, including progress data,
is now printed to the error log.