[MXS-4943] delayed_retry timeout errors do not have enough information Created: 2024-01-18  Updated: 2024-02-06  Resolved: 2024-02-06

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: 6.4.13, 22.08.11, 23.02.8, 23.08.4
Fix Version/s: 6.4.15, 22.08.12, 23.02.9, 23.08.5

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-201

 Description   

This is what is logged whenever the replaying of a query fails because it cannot find a valid candidate.

Write query received from user@127.0.0.1. ‘delayed_retry_timeout’ exceeded before a primary could be found. Closing client connection.

The problem is that when this error was logged, there was a valid server with the Master label available. If readwritesplit detects that a server with the correct state would be available but it cannot be used for some other reason, it should be included in the error.


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