Mysql state invalidating
I haven't touched anything such as reseting query cache for the year that the game has been up, I'm working with about 5000-1million rows depending on the table.
Everything is being updated constantly and things being inserted into the tables.
Since then the replication process lags a lot behind the master with the line in the process list of: invalidating query cache entries (table).
the global Were the size and type set to 0 when the server was started, or later?
The next time the current Impala node performs a query against a table whose metadata is invalidated, Impala reloads the associated metadata before the query proceeds.
If I understand correctly, every insert or update will clear the cache for that table?
That's what my searching online has found, I don't know if that's true though or if I should be regularly reseting the cache.
We are using Node JS with My SQL using pool with 10 connections. dev.mysql.com/doc/refman/5.6/en/Thank you for your interest in this question.
We were facing the issue of data being written by one connection and read by other and it was caching heavily. Thx, Note that the "Query cache" in My SQL is not a general page/blocks cache. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
So you should not normally need to call it explicitly except when you know that you've not fetched all the data from a statement handle.