[MXS-1506] Delayed query retry Created: 2017-10-30  Updated: 2018-04-13  Resolved: 2018-04-13

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: None
Fix Version/s: 2.3.0

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

Issue Links:
Blocks
blocks MXS-1723 Delayed connection creation Closed
Epic Link: Transparent master failover
Sprint: MXS-SPRINT-54, MXS-SPRINT-55

 Description   

Overview

If the connection to the master server is lost but a replacement is not immediately available, the retrying of the failed query needs to be delayed. The delay should be minimal meaning that the retrying is done as soon as a new master server is available.

Task Details

  • Add a way for routers to get notified of new servers
  • Create a mechanism that allows delayed execution of events

Implementation Details

To keep the retrying mechanism simple, the routers are not notified of new events but attempt to route the query again until either the routing is successful or a timeout is hit. This removes the need for separate retrying logic as the normal routing logic covers both cases.



 Comments   
Comment by markus makela [ 2018-04-13 ]

The delayed_retry parameter controls whether delayed query retrying is enabled.

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