29e5af1ded
Move router limitations to router documentation
...
This way the limitations are easier to find and are consistent across the
modules.
2019-05-17 14:44:49 +03:00
24ca503b0f
Document transaction_replay_attempts
...
Also added the new readwritesplit parameters to the 2.4.0 release notes.
2019-05-17 14:44:12 +03:00
0a6c94d77b
Merge branch '2.3' into develop
2019-05-16 10:55:19 +03:00
1dbe599b2a
Update 2.3.7 release date
...
Also remove the MXS-2475 'Fix mxs1980_blr_galera_server_ids_' "bug"
that was changed into a task as it has no impact on users of MaxScale.
2019-05-16 10:47:46 +03:00
74d912195a
Add release notes and update change log for 2.3.7
2019-05-15 09:11:40 +03:00
a163fa8a2c
Update release notes on reverse DNS option
2019-05-10 14:45:19 +03:00
0d13e694e4
Merge branch '2.3' into develop
2019-05-10 09:28:39 +03:00
034dc6a67e
MXS-2472 Update BLR docs on secondary masters
2019-05-09 17:14:57 +03:00
0423c5528e
Merge branch '2.3' into develop
2019-05-08 15:56:35 +03:00
5ea2bab88c
Merge branch '2.2' into 2.3
2019-05-08 15:56:08 +03:00
73f8bf1f6f
Update 2.2.21 release date
2019-05-08 15:49:11 +03:00
1df6495d9a
Update release notes on MariaDB-Monitor change
2019-05-08 15:32:08 +03:00
e3b5ba9620
MXS-1973 Support reverse DNS for client hostnames in MaxCtrl
...
May slow maxscale down when used. Only supported for "list sessions",
"show sessions" and "show session <id>".
2019-05-08 15:04:44 +03:00
a7a2215681
Update release notes and change log
2019-05-07 15:22:37 +03:00
5ac24de6b0
Remove log_to_shm
...
The feature was removed in 2.3 and was ignored if configured.
2019-05-06 16:05:50 +03:00
fb0745e3de
Merge branch '2.3' into develop
2019-05-03 13:48:57 +03:00
279edce16e
MXS-2457 Add treat_string_as_field to firewall
...
Necessary if the firewall should be able to block columns when
'ANSI_QUOTES' as enabled and " instead of backticks are used.
Without this, the following
> set @@sql_mode='ANSI_QUOTES';
> select "ssn" from person;
will not be blocked if the database firewall has been configured
to block the column ssn.
2019-05-03 13:38:12 +03:00
fe5160a714
MXS-2457 Add 'treat_string_arg_as_field' to DB Firewall
2019-05-03 13:38:12 +03:00
3a5a8b13b9
MXS-2457 Treat string args as fields
...
The masking filter will now consider all string arguments to
functions to be fields. This in order to prevent bypassing of
the masking with
> set @@sql_mode='ANSI_QUOTES';
> select concat("ssn") from masking;
This may lead to false positives, but no can do.
2019-05-03 13:38:12 +03:00
59be841939
MXS-2414: Rename max_auth_failures to max_auth_errors_until_block
2019-04-30 14:49:36 +03:00
6418bf017c
MXS-2414: Document max_auth_failures
2019-04-30 14:49:35 +03:00
2115322737
MXS-2329 Change warning into info
...
Currently it's too laborious to use duration suffixes when saving
generated configs and also to handle suffixes when changes are made
dynamically using maxctrl.
It will be trivial to do that when the new configuration mechanism
has been taken into use everywhere. That will not happen before
MaxScale 2.5.
So, in MaxScale 2.4 duration suffixes will be accepted in manually
created configuration files, but no warning will be logged if a
suffix is not used.
2019-04-30 13:02:53 +03:00
ccb3ea6157
MXS-2329 Update monitor tutorials
2019-04-30 13:02:53 +03:00
3d420dee6f
MXS-2329 Use durations in MariaDB monitor
2019-04-30 13:02:53 +03:00
b4518afba1
MXS-2329 Fix Aurora monitor documentation
2019-04-30 13:02:53 +03:00
c60c5e4626
MXS-2329 Use durations in monitor (common parts)
2019-04-30 13:02:53 +03:00
aa3057695b
MXS-2329 Use durations in schema router
2019-04-30 13:02:53 +03:00
ea243fd8ba
MXS-2329 Use durations in readwritesplit
2019-04-30 13:02:53 +03:00
0f5972e010
MXS-2329 Use durations with BLR:[heartbeat|connect_retry]
2019-04-30 13:02:53 +03:00
b1a495b342
MXS-2329 Use durations with persistmaxtime
2019-04-30 13:02:53 +03:00
93e130bb48
MXS-2329 Use durations with max_retry_interval
2019-04-30 13:02:53 +03:00
75fbcc9393
MXS-2329 Use durations in log_throttling
2019-04-30 13:02:53 +03:00
9fb4116bf5
MXS-2329 Use durations with connection_timeout
2019-04-30 13:02:53 +03:00
8bf0e00b1c
MXS-2329 Use duration with users_refresh_time
2019-04-30 13:02:53 +03:00
3055e49f5a
MXS-2329 Use durations with query_retry_timeout
...
Also change auth_[connect|read|write]_timeout to be time_t.
2019-04-30 13:02:53 +03:00
92cc31f0c0
MXS-2329 Use durations with auth_[connect|read|write]_timeout
2019-04-30 13:02:53 +03:00
810dc06d5c
Document removal of ndbclustermon and mmmon
2019-04-24 14:06:27 +03:00
88a9ca8b68
Document removal of debugcli and telnetd
2019-04-24 14:01:31 +03:00
4ad60fa2a2
Merge branch '2.3' into develop
2019-04-24 13:29:04 +03:00
b972d88bba
Merge branch '2.2' into 2.3
2019-04-24 12:51:32 +03:00
64a8288f66
MXS-2426 Document the change in cluster operation failure handling
2019-04-24 12:37:55 +03:00
4186f39616
Merge branch '2.3' into develop
2019-04-23 12:11:09 +03:00
111ab8f5e4
MXS-2441: Document galeramon changes
...
Added a section that describes how galeramon behaves when it is configured
to monitor non-Galera servers that are replicating from Galera nodes.
2019-04-23 11:57:10 +03:00
a8639c3226
Merge branch '2.3.6' into 2.3
2019-04-23 11:20:09 +03:00
2d8a93e88d
Update 2.3.6 release date
2019-04-23 11:17:01 +03:00
3e41a601f8
MXS-2411: Implicitly use latest API version
...
The request API prefix is now simply ignored as it has no meaning as long
as there is a single version of the API.
2019-04-18 13:58:34 +03:00
61f728c05a
MXS-2433: Reduce default query classifier cache size
...
Reduced the default cache size from 40% to 15%. Most cases don't benefit
from that much memory and the defaults have caused problems in live
environments.
2019-04-17 16:07:04 +03:00
b008c5a1e6
Add links to the sizes section
...
Links to the size type description in the documentation help explain what
sort of values are expected.
2019-04-17 14:10:48 +03:00
e9cc79d623
Fix typo in release notes
2019-04-17 09:31:49 +03:00
8b29e70f63
MXS-2428 Allow fixed Clustrix configuration
...
If 'dynamic_node_detection' has been set to false, then the
Clustrix monitor will not dynamically figure out what nodes are
available, but instead use the bootstrap nodes as such.
With 'dynamic_node_detection' being false, the Clustrix monitor
will do no cluster checks, but simply ping the health port of
each server.
2019-04-16 13:58:27 +03:00
