[MXS-3704] MaxScale always advertises the SESSION_TRACK capability even with servers that don't support it (XPand) Created: 2021-07-30 Updated: 2021-09-09 Resolved: 2021-08-02 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 2.5.12 |
| Fix Version/s: | 2.5.15, 6.1.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
If MaxScale is used with a XPand cluster, which doesn't support all the newer features that were introduced after MySQL 5.0, a client that expects the SESSION_TRACK functionality to work will not receive it. This also appears to be a problem with DBeaver which seems to query session_track_schema during its connection phase. The solution is to check if any of the servers used by a service doesn't support the SESSION_TRACK capability and disable it if there is one. |