[MXS-1467] MaxScale should monitor ColumnStore servers (UMs) for the ability to work with ColumnStore tables Created: 2017-10-09 Updated: 2020-08-25 Resolved: 2018-11-05 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Monitor |
| Affects Version/s: | None |
| Fix Version/s: | 2.3.1 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Valerii Kravchuk | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||
| Sprint: | MXS-SPRINT-67, MXS-SPRINT-68, MXS-SPRINT-69 | ||||||||||||||||||||
| Description |
|
When MaxScale monitors ColumnStore nodes, it's possible that the node is able to process any DML for non-ColumnStore tables, but ColumnStore data are not available there (PMs failed, for example). Monitors should check this, as it impacts the routing decisions. See https://jira.mariadb.org/browse/MCOL-962 for the related request to get the information needed available via SQL. |
| Comments |
| Comment by markus makela [ 2018-08-12 ] |
|
Related MCOL issue: https://jira.mariadb.org/browse/MCOL-962 |