I recently upgraded a replication slave from Percona Server 5.6 to the latest version of Percona Server 5.7.
We are using the TokuDB engine for many tables.
Now, the mysql log file is getting lots of entries likes this:
2016-03-24T03:29:59.950572Z 41 [Note] TokuDB: Auto scheduling background analysis for ./diggers_db/tblcurrent, delta_activity 1 is greater than 30 percent of 4 rows. - succeeded.
2016-03-24T03:29:59.960814Z 41 [Note] TokuDB: Auto scheduling background analysis for ./tilttray_db/tblcurrent, delta_activity 1 is greater than 30 percent of 3 rows. - succeeded.
2016-03-24T03:29:59.989689Z 41 [Note] TokuDB: Auto scheduling background analysis for ./luxury_db/tblcurrent, delta_activity 3 is greater than 30 percent of 13 rows. - succeeded.
2016-03-24T03:29:59.999439Z 41 [Note] TokuDB: Auto scheduling background analysis for ./valley_db/tblcurrent, delta_activity 2 is greater than 30 percent of 8 rows. - succeeded.
2016-03-24T03:30:00.054944Z 41 [Note] TokuDB: Auto scheduling background analysis for ./slab_db/tblcurrent, delta_activity 1 is greater than 30 percent of 5 rows. - succeeded.
The same database names are appearing again and again. I note that most of these tables are tiny, with between 1 and 20 rows. It’s been over a day since the upgrade and it’s still happening.
Perhaps this is a bug in the TokuDB analyze code causing it to schedule unnecessary analyze operations?
I see there are many configuration options to control the behaviour TokuDB analyze, but not sure if it is necessary to tweak these - I’d rather not stab in the dark.
Would appreciate expert advice. Thanks.