[MXS-2604] Requesting a shared cache betwenn several MaxScale instances Created: 2019-07-16 Updated: 2020-04-02 Resolved: 2019-09-04 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | cache, failover |
| Affects Version/s: | 2.3.9 |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | Sebastien GIRAUD | Assignee: | Todd Stoffel (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | performance | ||
| Environment: |
All |
||
| Description |
|
In order to have a full HA solution, and also to reduce the impact of a failover (moving from one MaxScale to another one), it could be great so shared the MaxScale cache to other MaxScale. This needs may be also integrated in a complete HA clustering solution dedicated to MaxScale. Several customers are requesting simple and fully integrated HA solution for MaxScale. |
| Comments |
| Comment by Todd Stoffel (Inactive) [ 2019-09-04 ] |
|
This would negatively impact performance of the current cache filter. |