[MXS-4214] Allow schemarouter caches to be refresh during off-peak hours Created: 2022-07-25  Updated: 2023-06-28  Resolved: 2023-06-28

Status: Closed
Project: MariaDB MaxScale
Component/s: schemarouter
Affects Version/s: None
Fix Version/s: 23.08.0

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

Sprint: MXS-SPRINT-184, MXS-SPRINT-185

 Description   

To minimize the impact of loading of the shard information, the cached could be marked to expire at a certain point in time instead of after a fixed time value. This would make it easier to warm up the caches before peak traffic happens.

An alternative approach to this would be to add a command for manually purging the cache which could then be automated with something like cron.



 Comments   
Comment by markus makela [ 2022-09-06 ]

If the somewhat low hanging fruit feature of MXS-4215 is implemented then this can be implemented with a normal cronjob that just calls a MaxCtrl command.

Comment by markus makela [ 2023-06-28 ]

This can now be implemented with the maxctrl call command schemarouter <service> invalidate.

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