Why use myisamchk
myisamchk is a tool used to check, repair, and optimize MyISAM tables. My company uses MyISAM tables to quickly update a large shared read only reference database. Normal dynamic data is kept in InnoDB tables and the MyISAM reference data is joined in queries. However, it’s worth noting that there are well documented issues, here and here, with mixing MyISAM and InnoDB tables together.
Cardinality is Key
The work flow of building the tables are:
- Pull data for many sources (third party)
- Compile data (app)
- build tables (lots of inserts)
- optimize (analyze and sort indexes)
- push to production (read only)
From this point we’re going to focus on the step 4, optimizing the table data.
After large amounts of data is inserted into a table, step 3 above, it is crucial to refresh the table indexes and give MySQL the best possible chance for the best query execution plan. To do this, you must run OPTIMIZE TABLE, ANALYZE TABLE or use the myisamchk tool when it is safe to use.
In this case the tables are being optimized outsize of MySQL, so the myisamchk command line comes in hand here. The command being ran to do this work:
[root@host]# myisamchk -vvv --analyze --sort-index test.MYI
When executed this output is displayed:
- Sorting index for MyISAM-table 'test.MYI'
At first this output looks normal, but anyone who has used myisamchk knows that the --analyze option outputs much more as show here:
[root@hoss]# myisamchk -vvv --analyze test.MYI
Checking MyISAM file: test.MYI
Data records: 60771 Deleted blocks: 0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2
- check data record references index: 3
The Problem / Bug
If the --sort-index option is used with the --analyze option, --sort-index is ignored without an error or warning from the program that the option will be ignored and only a sort index will be performed.
if (param->testflag & (T_REP_ANY | T_SORT_RECORDS | T_SORT_INDEX))
else if ((param->testflag & T_CHECK) || !(param->testflag & T_AUTO_INC))
If param->testflag is either T_SORT_RECORDS or T_SORT_INDEX, then the else if block that handles the T_CHECK / analyze is never execute.
- Update the documentation to note the --sort-index and --analyze options cannot be ran together.
- Update myisamchk to ignore and show a warning that both options cannot be ran together.
- Update myisamchk to allow for --sort-index and --analyze to be executed together.