[MXS-3973] Session capabilities are not frozen on session startup Created: 2022-02-01  Updated: 2022-02-03  Resolved: 2022-02-03

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.5.18
Fix Version/s: 2.5.19, 6.2.2

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


 Description   

If a filter is removed from a service at runtime and there are open sessions, the behavior of the session can change in ways that the existing filter sessions do not expect. In practice this is only a problem for services that use readconnroute with filters that require more complex processing e.g. the maxrows or cache filters. This can also affect other routers but it is less likely to cause problems as they already require a larger set of capabilities.

This could manifest as a hang after altering the filters of a service at runtime.


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