Hello Michael,
On 2015-05-15 00:44, Prof. Dr. Michael Schefczyk wrote:
As the database can grow quite large over time, I am running mailpiler
1.1.1 on a virtual machine which has /var/lib/mysql attached via nfs
from a NAS device. Once in a while after an unfriendly shutdown, the
database fails. The only practical solution I could find is to delete
the InnoDB files, start mysql, reimport the database from the last
backup and run a complete reindex. If possible, I would like the
database to survive an unfriendly shutdown without manual
intervention. My impression is that the old MyISAM storage engine
(while not transactional) is much more robust than InnoDB. Would it be
possible to change the engine in my.conf and in the tables back to
MyISAM without running into problems?
You don't have to reindex since it's for healing (or regenerating) the
sphinx database (which is a completely different story), not for fixing
a mysql related issue.
Anyway you are free to pick any storage engine of your choice, and
though
each of them has its own pros and cons, I believe that InnoDB (and its
derivatives) is a better choice than MyISAM. If you chose myisam, then
you have to convert the tables. Probably a good idea to stop piler while
you do it.
Btw. if you have little disk space on the archiving host, then consider
using a remote mysql server.
Janos
