This sounds very unusual for a table using the ARCHIVE Storage Engine. I had problems with 8.0.16 too - I ended up reinitialising the database and then loading a mysqldump from the earlier version as it was the quickest way to get up and running. Each new version only understands the file formats from a certain range of older versions. The challenge you're having with 8.0 is that going straight there from 5.5 is too big a jump for the updates needed to the data files. Make a note of them so you know what to install from 5.6. Use yum list mysql* or yum list installed | grep mysql to see what you have installed and what versions and then remove anything version 8 related with yum remove packagename. Make sure to protect the data files themselves and/or make copies. I would suggest uninstalling the current version with yum remove and then installing the version you want. Yum update will only replace an installed package with a newer version unless you tell it otherwise, so it won't downgrade your 8.0 installation even if the repository it came from has been disabled in its config files. Raising innodb_open_files to a big number should not be that all that troublesome, but please be sensible about the number you choose. Here is an additional reference from MySQL Performance Blog about setting innodb_open_files. General I/O tuning advice, see Section 8.5.7, “Optimizing InnoDB Disk Server option, and do not affect the operation of the table cache. They are independent of those specified by the -open-files-limit The higher of 300 and table_open_cache otherwise. The default value is 300 if innodb_file_per_table is not enabled, and ibd files that MySQLĬan keep open at one time.

This variable is relevant only if you use multiple InnoDB tablespaces. In MySQL 5.6, this setting is treated a little different. Since you are using InnoDB with innodb_file_per_table enabled, you need to raise innodb_open_files because this dictates the number of open file handles on. Version info: CRMPiccos-MacBook:log crmpicco$ mysql -version => Successfully started `mysql` (label: ) When I start MySQL with homebrew I get no error: CRMPiccos-MacBook:~ crmpicco$ brew services start mysql

This is how I initialised MySQL: mysqld -initialize -verbose -user=`whoami` -basedir='$(brew -prefix mysql)' -datadir=/usr/local/var/mysql I had to create a var/log/mysql/error.log as it wasn't created automatically, however now it is logging I get the following error when I do a rver start: T13:36:28.554840Z 0 Can't open the ugin table. I had a previous (non-functioning) install of MySQL so I followed the steps here to install a clean copy with Homebrew. I am attempting to install MySQL on macOS Sierra 10.12.5.

How to install mysql on mac sierra