TRACE logs on 56-5.6.42-rel84.2.el6.x86_64 (possible due to tokudb?)

Description

We run several Percona Server instances. They were updated from 56-5.6.41-rel84.1.el6.x86_64 to 56-5.6.42-rel84.2.el6.x86_64 and immediately all servers that also have tokudb installed are flooding huge amounts (few GB/hour) of TRACE events to mysqld.log, example:

Otherwise the server configurations are very similar between servers that log TRACE and servers that do not; I suspect the main issue is the presence of:

Percona-Server-tokudb-56-5.6.42-rel84.2.el6.x86_64

Other components on servers without the issue:
Percona-Server-shared-56-5.6.42-rel84.2.el6.x86_64
Percona-Server-client-56-5.6.42-rel84.2.el6.x86_64
Percona-Server-server-56-5.6.42-rel84.2.el6.x86_64

 

Config files could be given in private if needed.

Environment

EL7 with all updates

Smart Checklist

Activity

Show:

Artyom Konovalenko June 20, 2019 at 12:38 AM

The same problem with version 8.0.15:

Name : percona-server-tokudb
Arch : x86_64
Version : 8.0.15
Release : 6.1.el7
Size : 5.6 M
Repo : installed
From repo : percona-server80-oraclelinux7-x86_64

Gigabyte of logs in minutes.

Ville Ojamo December 20, 2018 at 11:43 AM

Sorry for the duplicate, I did a search for "TRACE" and found nothing relevant. Thanks for confirming. Is there a fix in roadmap?

Or since tokudb seems to be ~deprecated will it not be fixed?

Lalit Choudhary December 20, 2018 at 9:25 AM

Hello

Thank you for the report.

Cause for the extra TRACE in logs is 'Tokubackup'. Disable it will solve this problem. 

The issue already reported in .

Example:

 

after this, you will not see these TRACE in the error log.

Ville Ojamo December 19, 2018 at 10:48 AM

Addition: there are some other TRACE entries also that might be of interest:

Duplicate

Details

Assignee

Reporter

Components

Affects versions

Priority

Smart Checklist

Created December 19, 2018 at 10:45 AM
Updated March 6, 2024 at 12:32 PM
Resolved December 20, 2018 at 9:27 AM