Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
Description
It is well known that in concurrent environment running ANALYZE TABLE could lead to situation when hundreds of threads are in state "Waiting for table flush".
Percona had resolved this problem recently so that ANALYZE TABLE stops flushing affected tables from the table definition cache, see https://bugs.launchpad.net/percona-server/+bug/1704195 , https://github.com/percona/percona-server/pull/1977 etc for more details.
This is a request to implement the same/similar approach in MariaDB, maybe even 10.1+, but at least 10.3+.
Attachments
Issue Links
- relates to
-
MDEV-17882 Cleanup refresh version
-
- Closed
-
The patch in percona server is fairly small and should be applicable to MariaDB:
https://github.com/percona/percona-server/pull/1977/commits/cd7201514fee78aaf7d3eb2b28d2573c76f53b84
I don't quite understand these things yet:
objects with old statistics values will remain in use indefinitely? (Or,
InnoDB and TokuDB have a property that updated table statistics will start to
be used anyway, and so flushing the table is redundant?