On 14 Aug 2017, at 0:17, Carsten Strotmann wrote:
Dropping the retry value down further seems reasonable, maybe to 5
minutes. You always want your secondaries to have fresh data. If you
have secondaries that are having problems contacting you, you have an
operational problem. Maybe add some text to the new version
explaining
why this number is lower and suggesting that the watch the logs on
their
secondaries for failures to refresh.
We'll consider this. Care must be taken that once a server is not
reachable because of too much traffic, a too low RETRY value might
make
things worse. But I agree it is preferrable to have fast recovery.
The "retry" value only applies to secondary servers. If a master is
overloaded by thousands of customers, adding in its one or two secondary
servers will barely be noticed.
--Paul Hoffman
