The "innodb_read_only" parameter is perhaps not
among the most commonly used MySQL parameters. It may however
influence server behaviour in a way that you may not expect. This
post is a record of an investigation that revealed one of MySQL
quirks caused by said parameter.
Background The MySQL 5.6 server topology I was looking at during
this investigation consisted of a single main server (R/W) and
multiple replicas serving read-only statements.
This is relatively simple and you wouldn't expect to run into
issues on the replicas as long as you stick to statements that do
not modify data, right?
Not quite. Issue I was asked to investigate can be described as
follows:
The DBA created two tables connected using a foreign key
relationship:
CREATE TABLE `employee` ( `e_id` int(11) NOT …[Read more]
