[MXS-443] Network outages cause highly repetitive error reporting in the logs Created: 2015-11-03  Updated: 2016-10-17  Resolved: 2016-10-17

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

Type: Bug Priority: Minor
Reporter: martin brampton (Inactive) Assignee: Johan Wikman
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MXS-810 Error log is too verbose Closed

 Description   

The error handling does not have any memory. If, for example, a backend DB server loses its connection with MaxScale and the clients continue to attempt connections, the same error is reported repeatedly.

This causes excessive logging which makes log files hard to handle and masks other possible errors.

An example is:

2015-11-03 08:49:54 Error : Couldn't find suitable Master from 2 candidates.
2015-11-03 08:49:54 140736837035776 [session_alloc] Error : Failed to create RW Split Router session because routercould not establish a new router session, see earlier error.
2015-11-03 08:49:54 Error : Couldn't find suitable Master from 2 candidates.
2015-11-03 08:49:54 140736837035776 [session_alloc] Error : Failed to create RW Split Router session because routercould not establish a new router session, see earlier error.
2015-11-03 08:49:54 Error : Couldn't find suitable Master from 2 candidates.
2015-11-03 08:49:54 140736837035776 [session_alloc] Error : Failed to create RW Split Router session because routercould not establish a new router session, see earlier error.
2015-11-03 08:49:54 Error : Failed to create new routing session. Couldn't find eligible candidate server. Freeing allocated resources.
2015-11-03 08:49:54 140736837035776 [session_alloc] Error : Failed to create Read Connection Router session because routercould not establish a new router session, see earlier error.
2015-11-03 08:49:54 Error : Failed to create new routing session. Couldn't find eligible candidate server. Freeing allocated resources.
2015-11-03 08:49:54 140736837035776 [session_alloc] Error : Failed to create Read Connection Router session because routercould not establish a new router session, see earlier error.
2015-11-03 08:49:54 Error : Failed to create new routing session. Couldn't find eligible candidate server. Freeing allocated resources.
2015-11-03 08:49:54 140736837035776 [session_alloc] Error : Failed to create Read Connection Router session because routercould not establish a new router session, see earlier error.

which shows 12 errors being logged in one second, followed by many more in subsequent seconds, until the connection is restored.

 Comments   
Comment by Johan Wikman [ 2016-08-08 ]

Changed to a minor bug as MXS-823 should now handle the symptom.

A generic task MXS-824 created for providing a mechanism using which the actual problem can be handled.

Comment by Johan Wikman [ 2016-10-17 ]

The immediate problem is handled by MXS-823, and the general issue is captured by MXS-824.

Generated at Thu Feb 08 03:59:19 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.