[MXS-2301] Replica in RDS not detected as slave Created: 2019-01-29 Updated: 2021-08-02 Resolved: 2021-08-02 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | mariadbmon |
| Affects Version/s: | 2.3.3 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Lukasz | Assignee: | Esa Korhonen |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | aws | ||
| Environment: |
Ubuntu 18.04.1 LTS |
||
| Description |
|
Hi all, Since I've upgraded from maxscale-2.2.19-1.ubuntu.bionic.x86_64.deb to maxscale-2.3.3-1.ubuntu.xenial.x86_64.deb and the MaxScale stopped routing queries to replica running in RDS. The read replicas are now being detected as Slave of External Server and in result all queries including basic SELECT statements are now executed on Master.
Here is the result of the simple query:
|
| Comments |
| Comment by markus makela [ 2019-02-05 ] |
|
This might be caused by assume_unique_hostnames. See if adding assume_unique_hostnames=false solves it. |
| Comment by markus makela [ 2019-07-05 ] |
|
kucyk any updates? |
| Comment by Lukasz [ 2019-07-05 ] |
|
I've never found a way to get it to work, so I've downgraded to 2.2.19 and all is working perfectly fine since then. |
| Comment by markus makela [ 2020-10-19 ] |
|
kucyk have you been able to test the latest 2.5 release of MaxScale? |
| Comment by markus makela [ 2021-08-02 ] |
|
Closing as Cannot Reproduce. If you manage to reproduce this with one of the more recent releases, we'll reopen this. |