Log Throttling

In some circumstances, if MaxScale due to a persistent error, failure or some configuration issue fails to do something, it logs an error and tries again, leading to a situation where the log is flooded with the same error or set of errors being reported over and over again. MXS-810 and MXS and MXS-443 are examples of such a situation.

In general, MaxScale should be prepared for and deal explicitly with such situations; for instance, in some cases just aborting the connection, in others retrying with ever increasing intervals, or something else, so that the situation is dealt with without the log being flooded.

However, making sure that MaxScale would never flood the log is difficult, so a backup mechanism that simply throttles the logging, that is, a mechanism that deals with the symptom and not the cause, is needed.