[MXS-4438] On a restart, maxscale does not rediscover xpand nodes if proxy protocol is enabled Created: 2022-12-09 Updated: 2023-01-03 Resolved: 2023-01-03 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | xpandmon |
| Affects Version/s: | 6.4.4 |
| Fix Version/s: | 6.4.4 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Manjinder Nijjar | Assignee: | Esa Korhonen |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Sprint: | MXS-SPRINT-173, MXS-SPRINT-174 | ||||
| Description |
|
Maxscale 6.4.4 has a bug where in if Maxscale service starts (or restarts) after Proxy protocol has been set on Xpand (6.1_beta2), its not able to discover xpand nodes. This works fine with version 22.08.3. These are repro steps: Another way to repro this is to restart maxscale anytime after proxy_protocol is enabled on xpand and maxscale. Logs:
To get out of this situation, you do following on xpand:
Restart maxscale
Maxctrl does not work either:
|