Hi.
Thanks for noticing. I've updated the page: in MariaDB as of 10.0.10, the option is not deprecated.
In MySQL 5.6 it is, and there is new syntax in CHANGE MASTER to set the value, but it is not in MariaDB 10.0 (yet).
Regarding the question at serverfault.com (unrelated to the documentation issue):
The problem here is that master_retry_count works most of the time (errors upon reading packets, connecting to the master, etc.). But in some special cases, for example while trying to execute a query on master, such as SET master_heartbeat_period, if the query fails on whatever reason, the slave considers it a fatal error and gives up.
From all I see, it's a bug present in MariaDB, including current 10.0, and MySQL up to 5.5. It was fixed in MySQL 5.6: the error code returned upon query execution is checked against the list of "network failures", and if it's one of those, the connection retry happens as usual.
I think we need to merge the fix into 10.0, since it was committed as a part of a seemingly unrelated task, and thus can easily be missed.
Meanwhile, if you are concerned about this issue, configuring MASTER_HEARTBEAT_PERIOD = interval should make it go away, although of course disabling heartbeats can have other consequences if the slave has idle periods longer than slave_net_timeout – it will increase the number of reconnects. It's probably not a big deal when the connection is that poor, but should be taken into account anyway.
Hi.
Thanks for noticing. I've updated the page: in MariaDB as of 10.0.10, the option is not deprecated.
In MySQL 5.6 it is, and there is new syntax in CHANGE MASTER to set the value, but it is not in MariaDB 10.0 (yet).
Regarding the question at serverfault.com (unrelated to the documentation issue):
The problem here is that master_retry_count works most of the time (errors upon reading packets, connecting to the master, etc.). But in some special cases, for example while trying to execute a query on master, such as SET master_heartbeat_period, if the query fails on whatever reason, the slave considers it a fatal error and gives up.
From all I see, it's a bug present in MariaDB, including current 10.0, and MySQL up to 5.5. It was fixed in MySQL 5.6: the error code returned upon query execution is checked against the list of "network failures", and if it's one of those, the connection retry happens as usual.
I think we need to merge the fix into 10.0, since it was committed as a part of a seemingly unrelated task, and thus can easily be missed.
Meanwhile, if you are concerned about this issue, configuring MASTER_HEARTBEAT_PERIOD = interval should make it go away, although of course disabling heartbeats can have other consequences if the slave has idle periods longer than slave_net_timeout – it will increase the number of reconnects. It's probably not a big deal when the connection is that poor, but should be taken into account anyway.