[MXS-824] Provide mechanism that allows repeating errors to be handled sensibly Created: 2016-08-08  Updated: 2017-12-01  Resolved: 2017-03-20

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: None
Fix Version/s: N/A

Type: New Feature Priority: Major
Reporter: Johan Wikman Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None


 Description   

MXS-443 and MXS-810 are examples of the log being flooded because of MaxScale logging the same error over and over again.

A mechanism is needed that allows MaxScale or components of MaxScale to handle situations like that in a manner that does not flood the log; by aborting whatever was being done, by retrying with intervals of increasing length, something else.

MXS-823 handles the symptom but there should be mechanisms that allow the flooding to be handled at its core.

 Comments   
Comment by Johan Wikman [ 2017-03-20 ]

It's unlikely a general purpose mechanism can be provided.

Generated at Thu Feb 08 04:02:12 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.