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
e09a6c8100
MXS-2428 Add 'dynamic_node_detection' 'health_check_port'
...
'dynamic_node_detection' specifies whether the Clustrix monitor
should dynamically figure out what nodes there are, or just rely
upon static information.
'health_check_port' specifies the port to be used when perforing
the health check ping.
2019-04-16 13:58:27 +03:00
2f243b8f08
MXS-2349: Document socket
...
Added documentation for the parameter and changed the minimum required
server definition in the REST API.
2019-04-16 11:52:38 +03:00
3c188bf421
Merge branch '2.3' into develop
2019-04-16 11:23:49 +03:00
3a4bec921a
Update 2.3.6 Change log and Release notes.
2019-04-16 11:07:17 +03:00
f8a22d0ac0
MXS-2344 Add setting for enabling SSL for replication
...
If the monitor setting "replication_master_ssl" is set to on, any CHANGE MASTER TO-command
will have MASTER_SSL=1. If set to off or unset, MASTER_SSL is left unchanged to match existing
behaviour.
2019-04-15 19:15:45 +03:00
5af022cc9f
MXS-1662 Document admin_pam_readwrite_service and admin_pam_readonly_service
2019-04-15 13:28:44 +03:00
c643f9bc8d
Merge branch '2.3' into develop
2019-04-12 13:23:49 +03:00
1c87e2facf
Add changes to admin user hashing to release notes
2019-04-12 13:02:01 +03:00
139651c092
MXS-2253 Runtime ttl changes are made in seconds
...
Internally durations are stored in milliseconds but runtime changes
using SQL are made in seconds. Consequently, the provided value must
be multiplied by 1000 before being stored.
2019-04-11 15:53:45 +03:00
a102efa01f
Backport: Document the force option for set
...
Added documentation for the new option and mentioned it in the release
notes.
2019-04-09 09:43:19 +03:00
b54e67223f
MXS-2423: Add missing parameters to maxscale endpoint
...
Also updated the REST API documentation to include the newer output
(automating this update would be valuable).
2019-04-05 13:33:16 +03:00
2aa3515fc8
Merge commit '09cb4a885f88d30b5108d215dcdaa5163229a230' into develop
2019-04-04 14:34:17 +03:00
f812302d62
Document readwritesplit behavior with server states
2019-04-04 13:00:35 +03:00
09cb4a885f
Fix readconnroute name in examples
2019-04-03 12:57:05 +03:00
e3e66f8e90
MXS-2417: Add option to ignore persisted configs
...
The load_persisted_configs parameter now controls whether persisted
runtime changes are loaded on startup. The changes are still generated as
it persists the current state of MaxScale making problem analysis easier.
2019-04-03 12:57:05 +03:00
319d9fa1c5
Document the force option for set
...
Added documentation for the new option and mentioned it in the release
notes.
2019-04-02 14:21:54 +03:00
d7971fa44d
Merge branch '2.3' into develop
2019-04-02 12:48:33 +03:00
366fc6b8ee
MXS-2201: Document static parameters
...
Documented the list of parameters that cannot be changed at runtime.
2019-04-02 12:45:00 +03:00
2829baeab7
Merge branch '2.3' into develop
2019-04-02 12:35:36 +03:00
b42d38a3f6
Update release date
2019-04-02 12:34:11 +03:00
ab96606269
Merge branch '2.3' into develop
2019-04-01 15:41:52 +03:00
758fec5e2f
Update 2.3.5 Change Log and Release Notes
2019-04-01 15:39:59 +03:00
e659c6cc73
Merge branch '2.3' into develop
2019-04-01 13:24:30 +03:00
5346b24fa4
MXS-2393 Add parameter 'require_fully_parsed'
...
If set to true and if any of the other blocking related parameters
is true, then a statement that cannot be fully parsed will be blocked.
Default is true.
2019-04-01 10:52:52 +03:00
3977207d12
Update transaction_replay documentation
...
Removed the confusing paragraph.
2019-03-29 14:23:15 +02:00
4276514e27
MXS-2363 Add section to release notes
...
Also fix some minor other things in the relase notes.
2019-03-29 11:32:36 +02:00
4f8d6d1853
Fix transaction_replay documentation
...
The documentation stated that MVCC reads weren't safe with
transaction_replay when in reality they are not safe in general and
transaction_replay has no effect on it.
2019-03-29 10:35:41 +02:00
6aa846ebc7
MXS-1951: Document SO_REUSEPORT effects
...
Added a section into limitations and noted the effects in the release
notes.
2019-03-28 16:34:12 +02:00
841bdf4d0f
Merge branch '2.3' into develop
2019-03-28 15:33:09 +02:00
24c763d701
Update 2.3.5 release notes
2019-03-28 14:47:31 +02:00
dfd1d1e979
Update 2.3.5 release notes
2019-03-28 14:42:20 +02:00
