concurrent_insert=2 maintenace

If I’m running concurrent_insert=2 and i end up with a bunch of deleted empty rows

what’s the best way to clear those out?

shut down the server and run a myisamchk --sort ?

from what i’ve read concurrent_insert=2 , appends to the end of the table, ignoring deleted rows for storage. which would lead to empty deleted rows, aka a bunch of empty data in the .MYD . that’s what i got from reading the docs on it anyway.

OPTIMIZE table;

Of course, that will trigger at least a write lock while that takes place.