[MXS-4471] Table selection doesn't tolerate node failures Created: 2023-01-04  Updated: 2023-01-08  Resolved: 2023-01-08

Status: Closed
Project: MariaDB MaxScale
Component/s: schemarouter
Affects Version/s: 2.5.23, 6.4.4, 22.08.3
Fix Version/s: 6.4.5, 22.08.4

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


 Description   

If a table exists on more than one node, the selection of which node the query is routed to ends up choosing the first valid node but not the first valid node for which an open connection exists. This ends up causing problems if a node goes down but a second node would have a copy of that table. This is only of relevance when tables have redundant copies.


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