[MDEV-12322] MariaDB 10.1.19 - Error log - every 4 seconds error message "clustered index of the table and create temporary files" Created: 2017-03-21  Updated: 2017-04-19  Resolved: 2017-04-19

Status: Closed
Project: MariaDB Server
Component/s: Server, Storage Engine - InnoDB
Affects Version/s: 10.1.19
Fix Version/s: 10.1.23, 10.2.6

Type: Bug Priority: Major
Reporter: Ganesan Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Environment:

Microsoft Windows Server 2012 R2 Standard

Attachments: Text File Mariadb_errorlog_excess.txt    
Issue Links:
Duplicate
duplicates MDEV-10509 Excessive InnoDB logging on release s... Closed

 Description   

Every 4 seconds following errors logged in to error log.
I tried setting Global Variable

log_warnings=2
and tried
log_warnings=3

and tried
log_warnings=0

irrespective of setting above , the below error message continues
=======================================================================================

2017-03-21 14:42:20 12860 [Note] InnoDB: Online DDL : Start
2017-03-21 14:42:20 12860 [Note] InnoDB: Online DDL : Start reading clustered index of the table and create temporary files
2017-03-21 14:42:20 12860 [Note] InnoDB: Online DDL : End of reading clustered index of the table and create temporary files
2017-03-21 14:42:20 12860 [Note] InnoDB: Online DDL : Start merge-sorting index `id`-temporary- (1 / 1), estimated cost : 20.0000
2017-03-21 14:42:20 12860 [Note] InnoDB: Online DDL : End of merge-sorting index `id`-temporary- (1 / 1)
2017-03-21 14:42:20 12860 [Note] InnoDB: Online DDL : Start building index `id`-temporary- (1 / 1), estimated cost : 30.0000
2017-03-21 14:42:20 12860 [Note] InnoDB: Online DDL : End of building index `id`-temporary- (1 / 1)
2017-03-21 14:42:20 12860 [Note] InnoDB: Online DDL : Start applying row log
2017-03-21 14:42:20 12860 [Note] InnoDB: Online DDL : End of applying row log
2017-03-21 14:42:20 12860 [Note] InnoDB: Online DDL : Completed

=======================================================================================

Following statement is inside a stored procedure and the procedure is called in
scheduled event that repeats every on minute.
do you think following statement may be the reason for the above messages continuously in the error log

CREATE TEMPORARY TABLE tableau_reporting.temp310
SELECT id,
(SELECT rh FROM v1dm10_temp_hum_90days b WHERE b.id = a.id - 1) AS RH1,
(SELECT rh FROM v1dm10_temp_hum_90days b WHERE b.id = a.id - 2) AS RH2,
(SELECT rh FROM v1dm10_temp_hum_90days b WHERE b.id = a.id - 3) AS RH3,
(SELECT rh FROM v1dm10_temp_hum_90days b WHERE b.id = a.id - 4) AS RH4,
(SELECT RH_Zero_Counter FROM v1dm10_temp_hum_90days b WHERE b.id = a.id - 1) AS Sum1,
(SELECT RH_Zero_Counter FROM v1dm10_temp_hum_90days b WHERE b.id = a.id - 2) AS Sum2,
(SELECT RH_Zero_Counter FROM v1dm10_temp_hum_90days b WHERE b.id = a.id - 3) AS Sum3,
(SELECT RH_Zero_Counter FROM v1dm10_temp_hum_90days b WHERE b.id = a.id - 4) AS Sum4
FROM v1dm10_temp_hum_90days a
WHERE RH_Zero_Counter = 1 ;

CREATE INDEX id
ON tableau_reporting.temp310(id);

=======================================================================================

 Comments   
Comment by Marko Mäkelä [ 2017-03-22 ]

It would seem to me that we might not need any DDL progress reporting for temporary tables, because temporary tables usually are small and short-lived.
MDEV-10509 should remove the error log spam for all tables, replacing it with proper progress reporting.

Comment by Elena Stepanova [ 2017-04-19 ]

Fixed in scope of MDEV-10509.

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