[MXS-1446] Introduce the concept of active/passive to MaxScale Created: 2017-09-15  Updated: 2018-03-28  Resolved: 2017-09-28

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: None
Fix Version/s: 2.2.0

Type: Task Priority: Major
Reporter: Johan Wikman Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: ha_maxscale

Epic Link: MaxScale MRM
Sprint: 2017-42

 Description   

In active mode, MaxScale behaves in the normal manner.

In passive mode MaxScale

  • when started, will create all services, listener sockets, REST-API endpoint, etc. just like an active MaxScale will do,
  • will expect not to receive traffic (although it will not cause errors if it does),
  • will monitor the servers, and
  • will not launch external programs on the basis of state changes in the servers.

Whether or not MaxScale should start in active or passive mode should be configurable in the configuration file and also possible to indicate with a command line flag.



 Comments   
Comment by markus makela [ 2017-09-28 ]

MaxScale now has a global passive option that enables the passive mode. In this mode no failover scripts are executed.

In addition to this, the launching of the failover script is now implemented but the actual command being executed is still a dummy command.

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