On Tue, Aug 2, 2016 at 10:13 AM, Sergei Golubchik wrote:
> Hi, Rich!
>
> Shall we include it in packages together with ha_tokudb.so?
> Or is it too dangerous for that?
>
It depends on how prevalent this problem is. If there are just a few
instances of this problem, then maybe this tool should j
Hi, Rich!
Shall we include it in packages together with ha_tokudb.so?
Or is it too dangerous for that?
On Aug 02, Rich Prohaska wrote:
> Hello All,
>
> Sometimes, TokuDB gets left in a state where it thinks that parts of a
> table exist (as observed in TokuDB's file map), but not all of the
> un
Hello All,
Sometimes, TokuDB gets left in a state where it thinks that parts of a
table exist (as observed in TokuDB's file map), but not all of the
underlying files (the TokuDB data files and/or the frm file) exist. This
probably occurs due to the interaction between the non-transactional DDL
th
what is the working innodb workaround - i have 2 such stupid files over
7 years on one of our machines and did not found anything useful to get
rid of them
https://mariadb.com/blog/get-rid-orphaned-innodb-temporary-tables-right-way
rr
___
Mailing li
Am 29.07.2016 um 01:09 schrieb Reinis Rozitis:
Hello,
tldr - Is there a way (similarly as with the InnoDB workaround of DROP
TABLE `#mysql50##sql-..') to delete an orphaned TokuDB table (and/or
clean the information_schema.tokudb_file_map)?
what is the working innodb workaround - i have 2 suc
Hello,
tldr - Is there a way (similarly as with the InnoDB workaround of DROP TABLE
`#mysql50##sql-..') to delete an orphaned TokuDB table (and/or clean the
information_schema.tokudb_file_map)?
Or should I address this to Percona/Toku people?
The long version:
I have noticed on one db insta
6 matches
Mail list logo
