[MXS-179] Keep configuration changes in synch across MaxScale Mate Nodes Created: 2015-06-03  Updated: 2016-10-11  Resolved: 2015-06-18

Status: Closed
Project: MariaDB MaxScale
Component/s: Documentation
Affects Version/s: None
Fix Version/s: 1.2.0

Type: New Feature Priority: Major
Reporter: Dipti Joshi (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-192 Test Configuration synch across nodes Closed
relates to MXS-133 Testing MaxScale 1.2.0 Features Closed
Epic Link: MaxScale 1.2 Features

 Description   

MaxScale shall allow configuration changes made on one MaxScale to be synchronized to mate MaxScale nodes, when configured in HA setting(active-active or active-standby)

  • there can be more than one mate nodes configured to be synchronized with each MaxScale node
  • Linux facility lsyncd (daemon wrapper around rsyncd), should be used to achieve this.

 Comments   
Comment by Dipti Joshi (Inactive) [ 2015-06-10 ]

markus makela : Do we have have a document that will explain how to set this up ? Also list of test cases for this ?

Comment by markus makela [ 2015-06-12 ]

Test cases: https://docs.google.com/spreadsheets/d/1_79XDH5tAQWHbrGQVm6NAdT9Swn7ZOBmhnmcgP0899o/edit?usp=sharing
Documentation: https://github.com/mariadb-corporation/MaxScale/blob/MXS-179/Documentation/Reference/MaxScale-HA-with-lsyncd.md

Comment by markus makela [ 2015-06-18 ]

Merged into develop.

Generated at Thu Feb 08 03:57:22 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.