Please note the InnoDB Architecture (picture courtesy of Percona CTO Vadim Tkachenko)
If your database is read/write, I wrote about why InnoDB cannot allow multiple instances
Your only alternative would be to start InnoDB in read only mode (See my only post mentioning this How to start mysqld with read-only data directory? as well as the MySQL 5.6 Documentation for the ReadOnly InnoDB Setting).
If you have database is all MyISAM or a mix of InnoDB and MyISAM, your MyISAM tables would be very prone to being in crash state (Unfortunately, that is true even for a single mysqld instance).
Keep in mind that every time you open a MyISAM table, there is counter in the header of the MyISAM table that monitors how many open file handles a MyISAM table has (See my
Mar 15, 2012 answer to Why do MySQL tables crash? How do I prevent it?). If a single mysqld instance crashes, the table is consider crashed. This will pile up warnings in the error log stating the MyISAM table would have to be repaired. If this is the case for a single mysqld instance, it is far more likely to happen with multiple instances. This would be case even if a mysqld instance was started with innodb_read_only and read_only enabled.
Your mysql schema has some MyISAM tables in it. They are small. Even if they crashed, your could run REPAIR TABLE on them and fix them quickly but there is a 1 in a million chance of dealing with authentication issues if you cannot repair them.
Since you mentioned
.ini, I assume you are in Windows. When it comes to MySQL, file handling locking in Windows tending to be more strict that that of Linux. So, InnoDB might be more cumbersome or slower in read only mode.
- If your database is read/write, it's out of the question
- If your database is read only
- If your database has any MyISAM tables, there can become more subject to file handle count corruption or even data corruption
- If your database is all InnoDB, then it is possible.