c819271cab
Merge branch '2.3' into develop
2019-06-14 09:40:19 +03:00
0f3ec4f42e
Remove "allow_cluster_recovery" from test configs
...
The parameter has been removed.
2019-06-13 14:35:50 +03:00
0b10b27ffd
MXS-2518 Check connection distribution with Clustrix
...
Readconnroute, with default 'router_options', as well as readwritesplit
should cause the connections to be distributed evenly across all nodes.
2019-06-13 13:45:14 +03:00
a5898f83f9
Fix mysqlmon_rejoin_manual
...
Added some extra connection refreshing and monitor waiting. Unclear why this
is needed now but it seems to work.
2019-06-13 10:28:14 +03:00
a0fcf67993
Merge branch '2.3' into develop
2019-06-12 11:29:03 +03:00
b98ff222f0
Merge branch '2.3.8' into 2.3
2019-06-12 11:26:33 +03:00
9fd0d38797
Merge branch '2.3' into develop
2019-06-12 08:59:36 +03:00
6ca5143141
Make kill_query more robust
...
The test now uses an infinite loop in the SQL to make sure the execution
is interrupted.
2019-06-11 21:30:16 +03:00
5adc8fa5bd
Add missing HEAVY labels to big tests
2019-06-11 09:44:27 +03:00
9d1f094c45
MXS-2512 Add test for trx replay due to rollback
...
The test performs the following:
CREATE tbl (x INT PRIMARY KEY)
t1 t2
BEGIN BEGIN
INSERT INTO tbl VALUES (1)
SELECT * FROM tbl FOR UPDATE
That will cause t2 to wait.
INSERT INTO tbl VALUES (0)
That will cause t2 to be rolled back due to a deadlock.
Without transaction replay, the SELECT will return with an error.
With transaction replay, the deadlock error will be caught, the
transaction replayed and SELECT will return successfully.
2019-06-11 09:44:27 +03:00
5f5e402a32
Reconnect before find_field in mysqlmon_rejoin_manual
...
This appears to fix the test failure but the reason why it worked before
still remains a mystery.
2019-06-11 00:09:26 +03:00
662a2adaa1
Merge branch '2.3' into develop
2019-06-06 16:44:46 +03:00
65975a38e2
Add test for MXS-2355
...
The test attempts to log in using mysql_clear_password.
2019-06-06 16:36:36 +03:00
799e9d67e6
Merge branch '2.3' into develop
2019-06-06 16:05:30 +03:00
0469d57ede
Merge branch '2.3' of github.com:mariadb-corporation/MaxScale into 2.3
2019-06-05 14:53:28 +03:00
ba60b92612
Merge branch '2.3' into develop
2019-06-05 14:48:43 +03:00
f0c4fd5723
MXS-2250 Add test that reveals the problem
...
Before the MXS-2250 fix, the following ends with an error:
CREATE TEMPORARY TABLE t (f INT);
DESCRIBE t;
Reason is that the first is sent to the master (and the table will
not be replicated to slaves) and the latter to some slave.
2019-06-05 14:29:30 +03:00
16005c452e
run create_user* under sudo
2019-06-05 13:42:39 +03:00
de978be955
remove '-u root' from create_user*.sh
...
Call of MariaDB client from local machine with sudo with '-u root' parameter
does not work with 10.4
2019-06-05 12:57:46 +03:00
44d1b821c3
Merge branch '2.3' into develop
2019-06-03 13:54:55 +03:00
d88846fab4
MXS-2515: Add KILL QUERY test case
...
The test checks that queries are killed properly.
2019-05-31 14:01:16 +03:00
13b258a151
MXS-2464: Add test case
...
The bug appears when a session command that is executed on the master
fails. The logic in the code doesn't take this case into consideration
when it processes failed connections.
2019-05-31 14:01:15 +03:00
ed63493875
Return valid values for undefined mdbci variables
...
If a variable is not defined in the network configuration, a valid value
is returned.
2019-05-29 18:46:33 +03:00
84986dbf92
MXS-2520: Add test case
...
The test reproduces the problem and verifies that the fix works.
2019-05-29 18:46:33 +03:00
075ed00f58
MXS-2481 Fix rebase error
2019-05-28 12:43:21 +03:00
6e5f7fcfbf
MXS-2481 Add timeout and comments
...
When node is taken down, we don't wait forever.
Added comments that make it easier to follow the test when it
is running.
2019-05-28 12:36:21 +03:00
dcc7d195a3
MXS-2481 Add/fix copyright blurb
2019-05-28 12:36:21 +03:00
71b648e965
MXS-2481 Test transaction replay at group change
...
Take down a node other than the one we are connected to, which
will cause a group change error, and test that MaxScale catches
that and replay the transaction.
2019-05-28 12:36:21 +03:00
e0b397455d
MXS-2481 Check that server has changed
2019-05-28 12:36:21 +03:00
1c3ccfe254
MXS-2481 Factor out functionality
...
To be used by other test-case.
2019-05-28 12:36:21 +03:00
37e526eb8d
MXS-2481 Rename test
...
No other changes.
2019-05-28 12:36:21 +03:00
2bcee1be8b
MXS-2481 Test transaction replay when node goes down
...
Currently tests transaction replay when node goes down.
Group change test will be added and name of test will be
changed accordingly.
2019-05-28 12:36:21 +03:00
1bd82555d9
MXS-2481 Add Clustrix group change test skeleton
2019-05-28 12:36:21 +03:00
7b803f621c
MXS-2481 Change blurb
2019-05-28 12:36:21 +03:00
8a2c43d297
MXS-2481 Add configuration file template
2019-05-28 12:36:21 +03:00
18214b1aa2
MXS-2481 Add Clustrix module-command test
...
Softfailing should turn the state of a server to Drained.
2019-05-28 12:36:21 +03:00
c0a0bb86a0
MXS-2481 Add MaxRest functionality
...
- show_server
- call_command
2019-05-28 12:36:21 +03:00
c35d92eccc
MXS-2481 Check that node-absense leads to Down
...
If MaxScale cannot ping the health-check port of a node, the
state of the node should become 'Down'.
2019-05-28 12:36:21 +03:00
a8487a945a
MXS-2481 When Clustrix [un]block health port as well
...
In the case of Clustrix, it is not sufficient to block the MariaDB
port alone, but the health-check port must be blocked as well.
2019-05-28 12:36:21 +03:00
0d3a235851
MXS-2481 Allow [un]block-commands to be overriden
...
In the case of Clustrix, there are other ports to block as well.
2019-05-28 12:25:21 +03:00
5a26bd8ce5
MXS-2481 Rename MaxCtrl to MaxRest
...
So as not to believe that the program depends upon or uses
maxctrl.
2019-05-28 12:25:21 +03:00
97ad45125d
MXS-2481 Add simple Clustrix test
2019-05-28 12:25:21 +03:00
b837e24995
MXS-2481 Add MaxCtrl class to test framework
...
The purpose of this class is to make it easy from a test program
to access the output of the REST-API. Currently it provides only
the equivalent of "maxctrl list servers", but it can be extended
if and when additional needs arise.
Right now it's implemented so that curl is executed on the 0th
MaxScale instance, using the ssh mechanism of the test framework.
2019-05-28 12:25:21 +03:00
0f1e964192
Merge branch '2.3' into develop
2019-05-28 11:15:46 +03:00
4d3d6e9d06
MXS-2479 Extend pam authenticator test to use a customized pam service
...
The test now covers additional messages being sent by the pam api.
2019-05-28 11:04:53 +03:00
f79e8b108c
Log end of bug601 verbosely
...
The test appears to fail to connect to MaxScale due to unavailability of
connections. Theoretically, the improvement in accept speed due to
SO_REUSEPORT additions could explain the faster exhaustion of available
sockets.
2019-05-24 10:05:16 +03:00
e72abe3643
Fix object names in mxs2450_change_user_crash
2019-05-24 10:05:16 +03:00
9d80b42dc6
Fix mxs2300_history_pruning config
...
Names with whitespace are no longer supported.
2019-05-24 10:05:16 +03:00
c57764a84f
Fix no_password
...
The test used freed memory.
2019-05-24 10:05:16 +03:00
cb1e7b14b4
Remove debugcli from test configurations
...
The module has been removed in 2.4.
2019-05-24 10:05:15 +03:00
