CentOS 7

Please attach <datadir>/performance_schema/accounts.frm file.

Elena - No such file as "performance_schema/accounts.frm" exists

performance_schema.accounts can be queried, however:

select count(*) from performance_schema.accounts;

+----------+

| count(*) |

+----------+

|        5 |

+----------+

1 row in set (0.25 sec)

Your error log says "Cannot open table performance_schema/accounts from the internal data dictionary of InnoDB though the .frm file for the table exists", so at least at that point the file did exist. Are you still getting the crash? Does the error log still have this line? Are you sure you are looking at the same instance/datadir where the crash occurred?

The crash still occurs as submitted. performance_schema does not have actual frm files on disk since MDEV-4262

It does if you are in the process of upgrading from a previous version or from MySQL, or, more importantly, if somebody tampered with the datadir and intentionally or not put the frm file into a wrong place. Real performance schema tables have nothing to do with InnoDB, so the latter is a more likely theory – you'll get the exact same message if you create a table `accounts` somewhere else and then physically put accounts.frm into <datadir>/performance_schema. Miracles, on the other hand, are less likely.

So, if you are still getting the above-mentioned error (and not just a crash), please run select @@datadir on the running instance, and then ls -la <obtained value>/performance_schema, or otherwise find the frm file that the server finds. It is possible that the crash itself is unrelated to this particular table, but inspecting the file might give us a clue of what was done to the datadir to achieve this.

Here are the contents requested from the running instance. The crashing still occurs.

MariaDB [(none)]> select @@datadir;

+-----------------+

| @@datadir       |

+-----------------+

| /var/lib/mysql/ |

+-----------------+

1 row in set (0.00 sec)

[root ~]# ls -la /var/lib/mysql/performance_schema

total 308

drwx------.  2 mysql mysql     27 Nov 19  2016 .

drwxr-xr-x. 50 mysql mysql 589824 Oct  1 10:43 ..

-rw-rw----.  1 mysql mysql     61 Nov 19  2016 db.opt

[root ~]# cat /var/lib/mysql/performance_schema/db.opt

default-character-set=utf8

default-collation=utf8_general_ci

bmoore29, the crashing still occurs, I got it. But does the error message (about the orphan .frm file) still occur?

marko, any thoughts? Can InnoDB in any circumstances claim that the frm file is there when it is not?

The error message about the frm file occurs on every crash of this type when KEY_COLUMN_USAGE is queried.

The error message and crash also occurs after setting performance-schema=off and/or performance-schema-account-size=0 and executing a clean restart.

Is there any more information or a way forward on this issue? This issue is creating a high amount of pain with multiple crashes in our current production environment.

Do you have a core dump?

Can you do

SELECT * FROM INFORMATION_SCHEMA.KEY_COLUMN_USAGE WHERE TABLE_SCHEMA='xxx' AND TABLE_NAME='yyy'

for every table that you have? No need to paste the results here, but hopefully it'll allow to identify that one table that causes the crash.