[MXS-2395] Unable Load-Balancing(readconnroute) with MaxScale Created: 2019-03-19  Updated: 2020-03-02  Resolved: 2020-03-02

Status: Closed
Project: MariaDB MaxScale
Component/s: readconnroute, Router
Affects Version/s: 2.3.4
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Seonghwan Kim Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Environment:

VMware
3node GaleraCluster & MaxSacle & appserver


 Description   

Hi,
I have found some strange thing.
When using 2.2.16 and 2.2.20 then load-balancing is well.
But when I change version to 2.3.4 then unable to load-balancing.

Changed things are like below.
1.rpm -e maxscale-2.2.20-1.x86_64
2.rpm -Uvh maxscale-2.3.4-1.centos.7.x86_64.rpm
3.systemctl restart maxscale

But back to the 2.2.20 then load-balancing is again well.

I think, this is bug or routing configuration is changed.
How can I solve this problem???

Thank you.

[root@router ~]# cat /etc/maxscale.cnf
 
[maxscale]
 
threads=auto
 
 
 
[dbserv1]
 
type=server
 
address=192.168.116.111
 
port=3306
 
protocol=MariaDBBackend
 
 
 
[dbserv2]
 
type=server
 
address=192.168.116.112
 
port=3306
 
protocol=MariaDBBackend
 
 
 
[dbserv3]
 
type=server
 
address=192.168.116.113
 
port=3306
 
protocol=MariaDBBackend
 
 
 
[Galera-Monitor]
 
type=monitor
 
module=galeramon
 
servers=dbserv1, dbserv2, dbserv3
 
user=monitor_user
 
passwd=my_password
 
monitor_interval=2000
 
 
 
[Galera-Service]
 
type=service
 
router=readconnroute
 
router_options=synced
 
servers=dbserv1, dbserv2, dbserv3
 
user=maxscale
 
passwd=maxscale_pw
 
enable_root_user=true
 
 
 
[Galera-Listener]
 
type=listener
 
service=Galera-Service
 
protocol=MariaDBClient
 
port=4306
 
#socket=/tmp/DB.cluster
 
 
 
[CLI]
 
type=service
 
router=cli
 
 
 
[CLI-Listener]
 
type=listener
 
service=CLI
 
protocol=maxscaled
 
socket=default



 Comments   
Comment by markus makela [ 2019-03-19 ]

Can you do maxadmin list servers when load balancing is not working?

Comment by Seonghwan Kim [ 2019-03-20 ]

I attached that command's history.

[root@router ~]# maxadmin list services
Services.
--------------------------------------------------------------------------------
Service Name | Router Module | #Users | Total Sessions | Backend databases
--------------------------------------------------------------------------------
Galera-Service | readconnroute | 1 | 1 | dbserv1, dbserv2, dbserv3
CLI | cli | 2 | 2 |
--------------------------------------------------------------------------------

[root@router ~]# maxadmin list servers
Servers.
--------------------------------------------------------------------
Server | Address | Port | Connections | Status
--------------------------------------------------------------------
dbserv1 | 192.168.116.111 | 3306 | 0 | Slave, Synced, Running
dbserv2 | 192.168.116.112 | 3306 | 0 | Master, Synced, Running
dbserv3 | 192.168.116.113 | 3306 | 0 | Slave, Synced, Running
--------------------------------------------------------------------
[root@router ~]#
[root@router ~]# maxadmin list listeners
Listeners.
-----------------------------------------------------------------------------+-------
Name | Service Name | Protocol Module | Address | Port | State
-----------------------------------------------------------------------------+-------
Galera-Listener | Galera-Service | MariaDBClient | :: | 4306 | Running
CLI-Listener | CLI | maxscaled | default | 0 | Running
-----------------------------------------------------------------------------+-------

[root@router ~]#

Comment by markus makela [ 2019-03-20 ]
  • Do you get an error on the client side when you use 2.3?
  • Are there any errors in /var/log/maxscale/maxscale.log when this happens?
  • Can you connect through MaxScale with 2.3?
Comment by markus makela [ 2019-04-18 ]

Do you have more than one connection open? If not, please try with multiple open connections and see if it works.

Comment by markus makela [ 2019-10-28 ]

Seonghwan Kim any updates?

Comment by markus makela [ 2020-03-02 ]

Closing due to no feedback.

Generated at Thu Feb 08 04:13:48 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.