Merge branch '2.3.0' into 2.3

Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md

@@ -10,6 +10,12 @@ report at [Jira](https://jira.mariadb.org).
 
 ## Changed Features
 
+### maxadmin `list threads`
+
+Maxadmin `list threads` now shows the descriptor counts and load of
+the MaxScale worker threads. For details, please consult the
+maxadmin [documentation](../Reference/MaxAdmin.md).
+
 ### MaxCtrl `create monitor`
 
 The `create monitor` command now accepts a list of key-value parameters that are
@@ -109,14 +115,26 @@ connections, the smallest lag is used.
 
 With recent MariaDB Server versions, the monitor can check the disk space on the
 backends and detect if the server is running low. The monitor can be set to
-automatically switchover a master low on disk space. Slaves are instead set to
+automatically switchover a master low on disk space. Slaves can be set to
 maintenance mode. Disk space is also considered when selecting a new master for
-promotion.
+promotion. See
+[switchover_on_low_disk_space](../Monitors/MariaDB-Monitor.md#switchover_on_low_disk_space)
+and
+[maintenance_on_low_disk_space](../Monitors/MariaDB-Monitor.md#maintenance_on_low_disk_space)
+for more information.
 
 #### Replication reset feature
 
 The *reset-replication* monitor command deletes all slave connections and binary
-logs, and then sets up replication. Useful when data is in sync but gtid:s are not.
+logs, and then sets up replication. Useful when data is in sync but gtid:s are
+not.
+
+#### Scheduled events handling in failover/switchover/rejoin
+
+Server events lauched by the event scheduler thread are now handled during
+cluster modification operations. See
+[handle_server_events](../Monitors/MariaDB-Monitor.md#handle_server_events)
+for more information.
 
 #### Unused parameters
 
@@ -199,8 +217,9 @@ configure it.
 
 ### Runtime Configuration of the Cache
 
-With the variable `@maxscale.cache.enabled` it is now possible for a
+With the variables `@maxscale.cache.use` and `@maxscale.cache.populate`
-client to specify whether the cache should be used. Please see the
+it is now possible for a client to specify whether the cache should be
+used and/or populated. Please see the
 [Cache](../Filters/Cache.md) documentation for details.
 
 ### User Specified Syslog Facility and Level for Authentication Errors
@@ -223,8 +242,6 @@ SchemaRouter [documentation](../Routers/SchemaRouter.md) for details.
 The [throttlefilter](../Filters/Throttle.md) replaces and extends on the limit_queries
 functionality of [the Database Firewall filter](../Filters/Database-Firewall-Filter.md).
 
-### Interactive Mode for MaxCtrl
-
 ### ReadWriteSplit
 
 A set of new features have been added to readwritesplit.

Documentation/Upgrading/Upgrading-To-MaxScale-2.3.md

@@ -0,0 +1,39 @@
+# Upgrading MariaDB MaxScale from 2.2 to 2.3
+
+This document describes possible issues when upgrading MariaDB
+MaxScale from version 2.2 to 2.3.
+
+For more information about MariaDB MaxScale 2.3, please refer
+to the [ChangeLog](../Changelog.md).
+
+Before starting the upgrade, we recommend you back up your current
+configuration file.
+
+### `passwd` is no longer accepted
+
+In the configuration file, passwords for monitors and services must be
+specified using `password`; the support for the earlier deprecated
+`passwd` has been removed. That is, the following
+```
+[The-Service]
+type=service
+passwd=some-service-password
+...
+
+[The-Monitor]
+type=service
+passwd=some-monitor-password
+...
+```
+must be changed to
+```
+[The-Service]
+type=service
+password=some-service-password
+...
+
+[The-Monitor]
+type=service
+password=some-monitor-password
+...
+```