Cardinality=0 for all rows in a TokuDB table
I neglected to mention it here but is mentioned in TDB-2, be aware that there is the possibility of a negative performance impact by disabling partial evictions. It does not show everywhere and in some edge cases it may actually improve overall performance. So please keep a watchful eye on the instances where you change it.
BTW in my case, I do not perform any server restart, so it's perhaps another issue?
Ah thanks a lot, I've now disabled the partial_eviction on my side, I'll see if the row count continues to drop in my case.
There is a fix for this that will appear in the next release of Percona Server that is undergoing testing right now. It is being tracked in the new Percona TokuDB JIRA project here https://jira.percona.com/browse/TDB-2 and also discussed here in DB-1015.
Until the fix is released, you may try disabling tokudb_enable_partial_eviction following a row recount to help mitigate the problem.
It's there's still some issue with the row counter, especially with INSERT ... ON DUPLICATE KEY (see the comments on https://bugs.launchpad.net/percona-server/+bug/1651844). This issue is really annoying as it regularly messed up the whole server. Any chance we could have an update on this issue?