[MXS-541] Make changes in the configuration transactional Created: 2016-01-08  Updated: 2017-12-01  Resolved: 2016-11-22

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: None
Fix Version/s: N/A

Type: New Feature Priority: Major
Reporter: markus makela Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None

Epic Link: Dynamic Configuration of MaxScale

 Description   

Any modifications to the configuration of a running MaxScale instance should be made in transactions so that a valid and working configuration is always in use. This means that removal, modification and addition of the objects can be done without affecting MaxScale and once the changes are complete, they should either succeed or fail. If a configuration change fails, the previous configuration would stays as the active configuration.



 Comments   
Comment by Johan Wikman [ 2016-11-22 ]

This was created for 1.4. Either this is not relevant at the moment or there are now other tasks that covers this, so closing this as obsolete.

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