hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix tutorial configurations

Browse Source 
Removed the `socket` options from the network listeners.

Updated wording for the listener sections to only mention network
ports. This makes the tutorial more concise.
This commit is contained in:
Markus Mäkelä 2018-03-08 15:29:37 +02:00
parent c24f2c12e6
commit ea2da89743
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19
4 changed files with 10 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/Tutorials/Galera-Cluster-Connection-Routing-Tutorial.md
View File

@ -120,9 +120,8 @@ service=Galera Service
```
A listener must also define the protocol module it will use for the incoming
network protocol, currently this should be the MariaDBClient protocol for all
database listeners. The listener may then supply a network port to listen on
and/or a socket within the file system.
network protocol, currently this must be the `MariaDBClient` protocol for all
database listeners. The listener must also supply the network port to listen on.
```
[Galera Listener]
@ -130,7 +129,6 @@ type=listener
service=Galera Service
protocol=MariaDBClient
port=4306
socket=/tmp/DB.Cluster
```
An address parameter may be given if the listener is required to bind to a particular

5
Documentation/Tutorials/Galera-Cluster-Read-Write-Splitting-Tutorial.md
View File

@ -71,7 +71,9 @@ type=listener
service=Splitter Service
```
A listener must also define the protocol module it will use for the incoming network protocol, currently this should be the `MariaDBClient` protocol for all database listeners. The listener may then supply a network port to listen on and/or a socket within the file system.
A listener must also define the protocol module it will use for the incoming
network protocol, currently this must be the `MariaDBClient` protocol for all
database listeners. The listener must also supply the network port to listen on.
```
[Splitter Listener]
@ -79,7 +81,6 @@ type=listener
service=Splitter Service
protocol=MariaDBClient
port=3306
socket=/tmp/ClusterMaster
```
An address parameter may be given if the listener is required to bind to a particular network address when using hosts with multiple network addresses. The default behavior is to listen on all network interfaces.

5
Documentation/Tutorials/MariaDB-Replication-Connection-Routing-Tutorial.md
View File

@ -106,7 +106,9 @@ type=listener
service=Read-Service
```
A listener must also define the protocol module it will use for the incoming network protocol, currently this should be the MariaDBClient protocol for all database listeners. The listener may then supply a network port to listen on and/or a socket within the file system.
A listener must also define the protocol module it will use for the incoming
network protocol, currently this must be the `MariaDBClient` protocol for all
database listeners. The listener must also supply the network port to listen on.
```
[Write-Listener]
@ -114,7 +116,6 @@ type=listener
service=Write-Service
protocol=MariaDBClient
port=4306
socket=/tmp/ClusterMaster
[Read-Listener]
type=listener

6
Documentation/Tutorials/MariaDB-Replication-Read-Write-Splitting-Tutorial.md
View File

@ -106,9 +106,8 @@ service=Splitter Service
```
A listener must also define the protocol module it will use for the incoming
network protocol, currently this should be the `MariaDBClient` protocol for all
database listeners. The listener may then supply a network port to listen on
and/or a socket within the file system.
network protocol, currently this must be the `MariaDBClient` protocol for all
database listeners. The listener must also supply the network port to listen on.
```
[Splitter Listener]
@ -116,7 +115,6 @@ type=listener
service=Splitter Service
protocol=MariaDBClient
port=3306
socket=/tmp/ClusterMaster
```
An address parameter may be given if the listener is required to bind to a