[MDEV-6456] No progress indication for "Reading tablespace information from the .ibd files" Created: 2014-07-18  Updated: 2017-03-07  Resolved: 2014-07-22

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.12
Fix Version/s: 10.1.1

Type: Bug Priority: Major
Reporter: Sergei Petrunia Assignee: Sergei Petrunia
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
Relates
relates to MDEV-11027 InnoDB log recovery is too noisy Closed

 Description   

The "Reading tablespace information from the .ibd files" step during InnoDB recovery can take a long time but provides no information.

We should make it indicate progress being made, .e.g every 15 seconds.

 Comments   
Comment by Sergei Petrunia [ 2014-07-18 ]

Made a patch that prints messages like this:

140718  2:30:33 [Note] InnoDB: Starting crash recovery.
 
140718  2:30:33 [Note] InnoDB: Reading tablespace information from the .ibd files...
 
140718  2:30:49 [Note] InnoDB: Processed 429 .ibd/.isl files
 
140718  2:31:05 [Note] InnoDB: Processed 1045 .ibd/.isl files
 
140718  2:31:21 [Note] InnoDB: Processed 1562 .ibd/.isl files
 
140718  2:31:37 [Note] InnoDB: Processed 2299 .ibd/.isl files
 
140718  2:31:53 [Note] InnoDB: Processed 3234 .ibd/.isl files
 
140718  2:31:56 [Note] InnoDB: Restoring possible half-written data pages 
140718  2:31:56 [Note] InnoDB: from the doublewrite buffer...

messages are printed every 15 seconds.

Comment by Sergei Petrunia [ 2014-07-18 ]

Patch: http://lists.askmonty.org/pipermail/commits/2014-July/006354.html

Comment by Sergei Petrunia [ 2014-07-18 ]

Jan, could you please review?

Comment by Jan Lindström (Inactive) [ 2014-07-21 ]

Sergei,

Ok to push.

Generated at Thu Feb 08 07:12:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.