testing:

• execute all existing tests, but test package should not restart Maxscale between different test cases; instead of it test package simply change maxscale.cnf and sent 'config reload' command to maxscale

Test is:

• configure some servers (server1...server4, .106...109) and mysqlmon, do some tests
• change maxscale.cnf: same server names, but different IPs (server1...server4, .111...114), galeramon
• SIGHUP to Maxscale

result is:

MaxScale> show servers
Server 0x31076c0 (server1)
Server: 192.168.122.111
Status: Running
Protocol: MySQLBackend
Port: 3306
Node Id: -1
Master Id: -1
Repl Depth: -1
Number of connections: 0
Current no. of conns: 0
Current no. of operations: 0
Server 0x31075d0 (server2)
Server: 192.168.122.112
Status: Running
Protocol: MySQLBackend
Port: 3306
Node Id: -1
Master Id: -1
Repl Depth: -1
Number of connections: 0
Current no. of conns: 0
Current no. of operations: 0
Server 0x30faa80 (server3)
Server: 192.168.122.113
Status: Running
Protocol: MySQLBackend
Port: 3306
Node Id: -1
Master Id: -1
Repl Depth: -1
Number of connections: 0
Current no. of conns: 0
Current no. of operations: 0
Server 0x30fa970 (server4)
Server: 192.168.122.114
Status: Running
Protocol: MySQLBackend
Port: 3306
Node Id: -1
Master Id: -1
Repl Depth: -1
Number of connections: 0
Current no. of conns: 0
Current no. of operations: 0
Server 0x30e78e0 (server1)
Server: 192.168.122.106
Status: Master, Running
Protocol: MySQLBackend
Port: 3306
Server Version: 5.5.43-MariaDB-log
Node Id: 106
Master Id: 107
Repl Depth: 0
Number of connections: 3
Current no. of conns: 0
Current no. of operations: 0
Server 0x30e77d0 (server2)
Server: 192.168.122.107
Status: Master, Running
Protocol: MySQLBackend
Port: 3306
Server Version: 5.5.43-MariaDB-log
Node Id: 107
Master Id: 106
Repl Depth: 0
Number of connections: 243
Current no. of conns: 0
Current no. of operations: 0
MaxScale>

server1 and server2 are listed twice!

other commands also show strange things:

MaxScale> show monitors
Monitor: 0x30f2a10
Name: MySQL Monitor
Monitor running
Sampling interval: 8000 milliseconds
Detect Stale Master: disabled
Monitored servers: 192.168.122.106:3306, 192.168.122.107:3306
MaxScale>

MaxScale> show services
Service 0x3108030
Service: Read Connection Router
Router: readconnroute (0x7ff6d0f645e0)
State: Allocated
Started: Tue Jun 2 23:40:09 2015
Root user access: Disabled
Backend databases
192.168.122.114:3306 Protocol: MySQLBackend
192.168.122.113:3306 Protocol: MySQLBackend
192.168.122.112:3306 Protocol: MySQLBackend
192.168.122.111:3306 Protocol: MySQLBackend
Users data: 0x3109040
Total connections: 0
Currently connected: 0
Service 0x31077d0
Service: HTTPD Router
Router: testroute (0x7ff6b43e8520)
State: Allocated
Started: Tue Jun 2 23:40:09 2015
Root user access: Disabled
Backend databases
192.168.122.114:3306 Protocol: MySQLBackend
192.168.122.113:3306 Protocol: MySQLBackend
192.168.122.112:3306 Protocol: MySQLBackend
192.168.122.111:3306 Protocol: MySQLBackend
Users data: 0x31083b0
Total connections: 1
Currently connected: 1
Service 0x30e9570
Service: RW Split Router
Router: readwritesplit (0x7ff6d0d3f0a0)
State: Started
Number of router sessions: 124
Current no. of router sessions: 0
Number of queries forwarded: 44
Number of queries forwarded to master: 28
Number of queries forwarded to slave: 16
Number of queries forwarded to all: 124
Started: Tue Jun 2 21:59:56 2015
Root user access: Disabled
Filter chain: QLA
Backend databases
192.168.122.114:3306 Protocol: MySQLBackend
192.168.122.113:3306 Protocol: MySQLBackend
192.168.122.112:3306 Protocol: MySQLBackend
192.168.122.111:3306 Protocol: MySQLBackend
192.168.122.107:3306 Protocol: MySQLBackend
192.168.122.106:3306 Protocol: MySQLBackend
Users data: 0x30f3380
Total connections: 125
Currently connected: 1
Service 0x30e93e0
Service: Read Connection Router Slave
Router: readconnroute (0x7ff6d0f645e0)
State: Started
Number of router sessions: 0
Current no. of router sessions: 0
Number of queries forwarded: 0
Started: Tue Jun 2 21:59:56 2015
Root user access: Disabled
Filter chain: QLA
Backend databases
192.168.122.107:3306 Protocol: MySQLBackend
192.168.122.106:3306 Protocol: MySQLBackend
Users data: 0x30ff7a0
Total connections: 1
Currently connected: 1
Service 0x30e8af0
Service: Read Connection Router Master
Router: readconnroute (0x7ff6d0f645e0)
State: Started
Number of router sessions: 120
Current no. of router sessions: 0
Number of queries forwarded: 120
Started: Tue Jun 2 21:59:56 2015
Root user access: Disabled
Filter chain: QLA
Backend databases
192.168.122.107:3306 Protocol: MySQLBackend
192.168.122.106:3306 Protocol: MySQLBackend
Users data: 0x30ffd60
Total connections: 121
Currently connected: 1
Service 0x30e8280
Service: Debug Interface
Router: debugcli (0x7ff6d118d6e0)
State: Started
Started: Tue Jun 2 21:59:56 2015
Root user access: Disabled
Backend databases
Users data: 0x3105200
Total connections: 1
Currently connected: 1
Service 0x30e79f0
Service: CLI
Router: cli (0x7ff6d13b9c00)
State: Started
Started: Tue Jun 2 21:59:56 2015
Root user access: Disabled
Backend databases
Users data: 0x3103b00
Total connections: 9
Currently connected: 2
MaxScale>

it seems something is wrong with monitors reload and servers list reload

tturenko, markus makela - Is the issue Timofey commented above on June 2nd fixed now ?

yes, it is fixed.

tturenko is now doing regression with this feature

crash!

MXS-70 branch, readconn_slave test:

(gdb) bt
#0 0x00000000005413b4 in config_get_paramtype (param=0x0) at /home/ec2-user/workspace/server/core/config.c:1114
#1 0x00007fd8e52bb298 in refreshInstance (router=0x394e8d0, singleparam=0x0)
at /home/ec2-user/workspace/server/modules/routing/readwritesplit/readwritesplit.c:420
#2 0x00007fd8e52bb7c6 in updateInstance (instance=0x394e8d0, service=0x39f4a00, options=0x39fe690)
at /home/ec2-user/workspace/server/modules/routing/readwritesplit/readwritesplit.c:668
#3 0x0000000000537efb in serviceUpdateRouter (service=0x39f4a00, context=0x3a116c0) at /home/ec2-user/workspace/server/core/service.c:1305
#4 0x0000000000543ecb in config_service_update_objects (obj=0x3a0f000, context=0x3a116c0) at /home/ec2-user/workspace/server/core/config.c:2478
#5 0x0000000000541eff in process_config_update (context=0x3a116c0) at /home/ec2-user/workspace/server/core/config.c:1543
#6 0x000000000053f5d5 in config_reload () at /home/ec2-user/workspace/server/core/config.c:311
#7 0x0000000000524915 in sighup_handler (i=1) at /home/ec2-user/workspace/server/core/gateway.c:284
#8 <signal handler called>
#9 0x00007fd8ec017f03 in epoll_wait () from /lib64/libc.so.6
#10 0x000000000053c547 in poll_waitevents (arg=0x0) at /home/ec2-user/workspace/server/core/poll.c:502
#11 0x0000000000527900 in main (argc=2, argv=0x7fffcb945778) at /home/ec2-user/workspace/server/core/gateway.c:1788

The crash was due to a null check only after the value was used. It has been fixed.

Related to the dynamic configuration loading, which was abandoned. Let's create a similar task anew once it gets relevant again.