[MXS-1204] Try out MaxScale + keepalived Created: 2017-03-29 Updated: 2017-09-05 Resolved: 2017-09-05 |
|
| 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: | Esa Korhonen |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2017-35, 2017-37, 2017-38, 2017-39, 2017-40, 2017-41 |
| Description |
|
Try out a HA setup with keepalived + MaxScale. Make notes and write documentation how to properly setup such a configuration. |
| Comments |
| Comment by Esa Korhonen [ 2017-06-02 ] |
|
Tested in a LAN with the following setup: With the keepalived configured (correct network interface, virtual IP within LAN address space) and running, the Host3 will connect (using the VIP) to the MaxScale with the highest priority keepalived running. If then the highest priority machine goes down (or just the keepalived service on it stops), the second (in priority) MaxScale takes over. Any existing connections will break. |
| Comment by Esa Korhonen [ 2017-09-05 ] |
|
Closing for now. A test has been performed, blog post written. May still require a real regression test but that requires changes in test framework. |