47f5f2f0cc
Set Xpand version to 'latest' in system-test
...
Now MDBCI is able to find latest version of XPand automatically
2020-11-25 16:19:50 +02:00
27528628e2
Merge branch '2.4.14' into 2.4
2020-11-24 13:56:38 +02:00
885077b4d0
Avoid using test.repl->N in MariaDBMonitor tests
...
The value may not match the nodes used by the test.
2020-11-24 12:31:15 +02:00
abd1efefc6
Group Galera tests correctly
...
Grouping tests that require Galera backend together delays the creation of
those backends until they are needed.
2020-11-24 11:16:45 +02:00
3003ad6385
Remove Python tests
...
The tests are not very good and require custom Python modules to be
installed. In addition, they were written for Python2 which is no longer
available on all modern systems.
2020-11-24 11:16:27 +02:00
454e9aca14
Stop timeout before finishing test
...
This helps distinguish actual timeouts that happen during the test and
timeouts that happen during the test shutdown.
2020-11-24 11:16:27 +02:00
36f2af810a
2.4.14 Fix xpand_basics
...
The test assumed a certain node would always be present. Now the
test figures out what id to use.
Also fix broken clustrix -> xpand renaming.
2020-11-23 13:16:02 +02:00
6c160a3529
Log query classification info for session_trace
...
This fixes the bug where the detailed query classification info was only
logged when LOG_INFO was globally enabled.
2020-11-23 13:13:19 +02:00
0fe6f70458
Merge branch '2.4.14' into 2.4
2020-11-23 12:48:24 +02:00
26c7aa4c34
Fix xpand_transaction_replay configuration
...
The test expected rollbacks to be automatically replayed without it being
configured.
2020-11-23 11:55:01 +02:00
5906f59344
Merge branch '2.4' into 2.4.14
2020-11-19 13:54:55 +02:00
56575882d7
MXS-3301 Rename clustrix -> xpand everywhere
2020-11-19 13:44:06 +02:00
47e1c04d09
MXS-3301 Look for "xpand" to find out whether server is Xpand
...
We will continue to look for "clustrix" as well so that MaxScale
will continue to work with older releases.
2020-11-19 13:43:30 +02:00
266c866b18
2.4.14 Fix xpand_transaction_replay config
2020-11-19 13:40:57 +02:00
a0922a2451
2.4.14 Fix xpand cluster setup
2020-11-19 13:37:14 +02:00
f2f2e66da3
Merge branch '2.3' into 2.4
2020-11-19 09:42:36 +02:00
41caccbf4b
Separate MariaDB installation and Galera configuration
...
MDBCI now supports separate Galera server .cnf configuring.
Changing MDBCI config template in order to use this MDBCI
capability. It allows to use any MariaDB product in the
backend (Community or Enterprise, production, staging or CI)
2020-11-18 19:12:24 +02:00
32b1ca147e
Merge branch '2.3' into 2.4
2020-11-18 15:36:13 +02:00
4300f1d80e
Add a check for the existence of the LastTestsFailed.log file to rest… ( #213 )
...
Remove rerun failed tests
2020-11-18 15:35:42 +02:00
ed3e1ac2ec
use MDBCI to install Kerberos
2020-11-18 15:33:57 +02:00
5fc73646a4
MXS-3301 Rename clustrix -> xpand everywhere
2020-11-18 10:02:02 +02:00
9ed51b69e1
MXS-3301 Look for "xpand" to find out whether server is Xpand
...
We will continue to look for "clustrix" as well so that MaxScale
will continue to work with older releases.
2020-11-17 17:30:50 +02:00
64ca695c84
Revert "MXS-3301 Look for "xpand" to find out whether server is Xpand"
...
This reverts commit 4728730510409fc15d2b3a55fa6e00008651794d.
The clustrix -> xpand name change causes too much trouble when merging
to 2.5.
2020-11-17 17:21:14 +02:00
4728730510
MXS-3301 Look for "xpand" to find out whether server is Xpand
...
We will continue to look for "clustrix" as well so that MaxScale
will continue to work with older releases. Clustrix was replaced with
xpand in all symbols.
2020-11-17 13:25:13 +02:00
10582a02fe
Merge branch '2.3' into 2.4
2020-11-17 10:54:58 +02:00
f577d09829
MXS-3297: Don't advertise unsupported capabilities
...
Only bulk execute is supported. Supporting progress reporting currently
breaks the protocol result processing code.
2020-11-17 10:45:03 +02:00
fa0b9d8df1
Install one ASAN, not both
...
Installing both seems to cause problems on CentOS 7.
2020-11-17 10:09:19 +02:00
4545b8f798
Fix division by zero
...
If the query failed instantly it would crash the test.
2020-11-17 10:08:15 +02:00
558bd9279b
Use same script for both SSL and non-SSL users
2020-11-16 16:54:37 +02:00
c49a28ef12
2.4 Update maintenance release
2020-11-16 14:35:31 +02:00
03e904a33b
2.4.14 Add release notes and update change log
2020-11-16 14:27:53 +02:00
df36ef86d0
2.4.14 Update Change Date
2020-11-16 14:23:26 +02:00
5a33d45d4d
Merge branch '2.3' into 2.4
2020-11-16 09:25:43 +02:00
43c53e2f79
MXS-3297: Fix reading of extended MariaDB capabilities
...
The byte offset didn't take the size of the charset into account.
2020-11-16 09:20:51 +02:00
9dd736d4eb
MXS-3245: Document /v1/maxscale/ REST API responses
2020-11-16 09:20:51 +02:00
c49f17f428
MXS-3295: Fix layout of the classify endpoint
...
The values were stored in the parameters object which is used for
configuration parameters in other endpoints. The proper place for them is
inside the attributes object.
2020-11-16 09:20:50 +02:00
9edbca34c8
Fix ASAN library installation
...
The code used a newer compiler with an older ASAN library.
2020-11-13 10:40:46 +02:00
87cb6f76a1
Merge branch '2.3' into 2.4
2020-11-11 15:04:51 +02:00
a1a1bdf93d
MXS-3292 Fix bug
...
The string given to USE must be dequoted before being stored.
2020-11-11 12:37:36 +02:00
b459b6f13f
MXS-3292 Add test that reveals bug
2020-11-11 12:37:36 +02:00
e685741642
Configure SSL before starting MaxScale
...
This makes sure that the servers are correctly configured before MaxScale
sees them.
2020-11-11 11:22:59 +02:00
63ed377e3a
Merge branch '2.3' into 2.4
2020-11-10 10:13:32 +02:00
7b1625d65f
MXS-3272: Ask password first
...
The interactive would give the prompt first before asking for the
password. By copying the code from common.js, the password is always asked
first.
2020-11-09 17:33:34 +02:00
968d43799f
MXS-3273: Ignore unexpected responses
...
Unlike readwritesplit, schemarouter will process all responses from
backends as if they are expected. There are cases where errors are
generated that aren't sent as a response to a query. These queries must be
ignored and not routed to the client. Copying the code as-is from
readwritesplit isn't the cleanest solution but it avoids refactoring code
in a patch release.
The custom error number (2003) used by the backend protocol code was not
an actual error number that the server would send. The error code in
question was for an error that only the C connector returns:
CR_CONN_HOST_ERROR. Using ER_CONNECTION_KILLED as the error number better
conveys the fact that the connection was killed due to a reason not
related to any ongoing query.
By using a known error number that is correctly handled, we also avoid
writing errors to the client in the middle of a resultset or as the
initial response to a result. This explains why the problem described in
MXS-3267 happened in the first place: an unrelated connection was lost in
the middle of a resultset and the error was interpreted as the end of a
resultset. As a result of there being more data to be read, the unexpected
result state messages were logged.
2020-11-04 16:44:46 +02:00
e1ede4fed0
Merge branch '2.4' of github.com:mariadb-corporation/MaxScale into 2.4
2020-11-04 13:03:21 +02:00
6a3cf164e4
Merge remote-tracking branch 'origin/2.4.13' into 2.4
2020-11-04 13:03:00 +02:00
7efe15e0e6
Add note regarding new signature key
2020-11-04 12:55:58 +02:00
87f97a16c3
Log server name in error message
...
This makes it clear which server failed.
2020-10-29 15:33:48 +02:00
11368e5ed0
Merge branch '2.3' into 2.4
2020-10-29 15:25:21 +02:00
46dab1e884
MXS-3259: Add default connection timeout
...
The connector never times out if one is not defined. This seems to help
make the mxs1985_kill_hang test a lot more stable.
2020-10-29 15:12:49 +02:00
