Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.4.0, 1.4.1
-
None
-
Debian 8.4 amd64 KVM
Description
Up until version 1.3.0 of MaxScale it was possible to define separate listeners on different IP address but using the same port like so:
[Read-Write Service]
|
type=service
|
router=readwritesplit
|
servers=myc1d1,myc1d2
|
user=auser
|
passwd=secretpw
|
master_accept_reads=true
|
use_sql_variables_in=master
|
|
|
[Read-Write Listener]
|
type=listener
|
service=Read-Write Service
|
protocol=MySQLClient
|
address=172.16.49.70
|
port=3306
|
|
|
[Internal-RW Listener]
|
type=listener
|
service=Read-Write Service
|
protocol=MySQLClient
|
address=192.168.129.240
|
port=3306
|
Since MaxScale 1.4.0 the same config will result in:
Apr 4 22:53:08 myc1-dev-01 maxscale[10481]: Initialise readconnroute router module V1.1.0.
|
Apr 4 22:53:08 myc1-dev-01 maxscale[10481]: Loaded module readconnroute: V1.1.0 from /usr/lib/x86_64-linux-gnu/maxscale/libreadconnroute.so
|
Apr 4 22:53:08 myc1-dev-01 maxscale[10481]: Listener 'Read-Write Listener', for service 'Read-Write Service', already have port 3306.
|
And the MaxScale service refusing to start. Expected behavior would be the one from 1.3.0: just work.