Remove trailing whitespace from documentation
Removed trailing whitespace from all documents.
This commit is contained in:
Markus Mäkelä
parent
4050cd20d8
commit
8a2112cce6
@ -82,7 +82,7 @@ For more details, please refer to [MariaDB MaxScale 1.3 Release Notes](Release-N
|
||||
* Firewall filter
|
||||
* Multi-Master monitor
|
||||
* RabbitMQ logging filter
|
||||
* Schema Sharding router
|
||||
* Schema Sharding router
|
||||
* Added option to use high precision timestamps in logging.
|
||||
* Readwritesplit router now returns the master server's response.
|
||||
* New readwritesplit router option added. It is now possible to control the amount of memory readwritesplit sessions will consume by limiting the amount of session modifying statements they can execute.
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -49,7 +49,7 @@ The entry points for the Lua script expect the following signatures:
|
||||
- The `closeSession` function in the Lua scripts will be called.
|
||||
|
||||
- `(nil | bool | string) routeQuery(string)` - query is being routed
|
||||
|
||||
|
||||
- The Luafilter calls the `routeQuery` functions of both the session and the
|
||||
global script. The query is passed as a string parameter to the
|
||||
routeQuery Lua function and the return values of the session specific
|
||||
|
||||
@ -67,7 +67,7 @@ configured into the separate `consumer.cnf` file.
|
||||
| user | Username for the RabbitMQ server |
|
||||
| passwd | Password for the RabbitMQ server |
|
||||
| queue | Queue to consume from |
|
||||
| dbserver | Hostname of the SQL server |
|
||||
| dbserver | Hostname of the SQL server |
|
||||
| dbport | Port of the SQL server |
|
||||
| dbname | Name of the SQL database to use |
|
||||
| dbuser | Database username |
|
||||
|
||||
@ -30,7 +30,7 @@ filters=MyRegexfilter
|
||||
|
||||
## Filter Options
|
||||
|
||||
The Regex filter accepts the options ignorecase or case. These define if the pattern text should take the case of the string it is matching against into consideration or not.
|
||||
The Regex filter accepts the options ignorecase or case. These define if the pattern text should take the case of the string it is matching against into consideration or not.
|
||||
|
||||
## Filter Parameters
|
||||
|
||||
|
||||
@ -210,6 +210,6 @@ Average statement execution time 1.488 seconds
|
||||
|
||||
Total connection time 46.500 seconds
|
||||
|
||||
-bash-4.1$
|
||||
-bash-4.1$
|
||||
|
||||
```
|
||||
|
||||
@ -47,7 +47,7 @@ filename=/tmp/SqlQueryLog
|
||||
|
||||
### Source
|
||||
|
||||
The optional `source` parameter defines an address that is used
|
||||
The optional `source` parameter defines an address that is used
|
||||
to match against the address from which the client connection
|
||||
to MaxScale originates. Only sessions that originate from this
|
||||
address will be logged.
|
||||
@ -95,11 +95,11 @@ disabled when the router receives the character '0' from this named pipe.
|
||||
The default named pipe is **`/tmp/tpmfilter`** and logging is **disabled** by default.
|
||||
|
||||
named_pipe=/tmp/tpmfilter
|
||||
|
||||
|
||||
For example, the following command enables the logging:
|
||||
|
||||
$ echo '1' > /tmp/tpmfilter
|
||||
|
||||
|
||||
Similarly, the following command disables the logging:
|
||||
|
||||
$ echo '0' > /tmp/tpmfilter
|
||||
|
||||
@ -40,7 +40,7 @@ disable_master_failback=true
|
||||
|
||||
### `available_when_donor`
|
||||
|
||||
This option only has an effect if there is a single Galera node being backed up an XtraBackup instance. This causes the initial node to go into Donor state which would normally prevent if from being marked as a valid server inside MaxScale. If this option is enabled, a single node in Donor state where the method is XtraBackup will be kept in Synced state.
|
||||
This option only has an effect if there is a single Galera node being backed up an XtraBackup instance. This causes the initial node to go into Donor state which would normally prevent if from being marked as a valid server inside MaxScale. If this option is enabled, a single node in Donor state where the method is XtraBackup will be kept in Synced state.
|
||||
|
||||
```
|
||||
available_when_donor=true
|
||||
@ -93,7 +93,7 @@ Example of variable being set in all slave nodes, assuming three nodes:
|
||||
SET GLOBAL wsrep_sst_donor = "galera001,galera000"
|
||||
```
|
||||
|
||||
**Note**:
|
||||
**Note**:
|
||||
in order to set the global variable _wsrep_sst_donor_, proper privileges are
|
||||
required for the monitor user that connects to cluster nodes.
|
||||
This option is disabled by default and was introduced in MaxScale 2.1.0.
|
||||
@ -147,7 +147,7 @@ In this example `node-1` is always used as the master if available. If `node-1`
|
||||
is not available, then the next node with the highest priority rank is used. In
|
||||
this case it would be `node-3`. If both `node-1` and `node-3` were down, then
|
||||
`node-2` would be used. Because `node-4` has a value of 0 in _priority_, it will
|
||||
never be the master. Nodes without _priority_ parameter are considered as
|
||||
never be the master. Nodes without _priority_ parameter are considered as
|
||||
having the lowest priority rank and will be used only if all nodes
|
||||
with _priority_ parameter are not available.
|
||||
|
||||
|
||||
@ -37,7 +37,7 @@ All hints must start with the `maxscale` tag.
|
||||
|
||||
```
|
||||
-- maxscale <hint body>
|
||||
```
|
||||
```
|
||||
|
||||
The hints have two types, ones that define a server type and others that contain
|
||||
name-value pairs.
|
||||
|
||||
@ -557,7 +557,7 @@ RWSplit | readwritesplit | 1 | 1 | server
|
||||
SchemaRouter | schemarouter | 1 | 1 | server1, server2, server3, server4
|
||||
RWSplit-Hint | readwritesplit | 1 | 1 | server1, server2, server3, server4
|
||||
ReadConn | readconnroute | 1 | 1 | server1
|
||||
CLI | cli | 2 | 2 |
|
||||
CLI | cli | 2 | 2 |
|
||||
--------------------------+-------------------+--------+----------------+-------------------
|
||||
MaxScale>
|
||||
```
|
||||
@ -618,7 +618,7 @@ MaxScale> show service RWSplit
|
||||
[127.0.0.1]:3003 Protocol: MySQLBackend Name: server4
|
||||
Total connections: 1
|
||||
Currently connected: 1
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
This allows the set of backend servers defined by the service to be seen along
|
||||
@ -634,8 +634,8 @@ command can be used to examine the user data held by MariaDB MaxScale.
|
||||
|
||||
```
|
||||
MaxScale> show dbusers RWSplit
|
||||
User names: @localhost @localhost.localdomain 14567USER@localhost monuser@localhost monuser@% 14609USER@localhost maxuser@localhost maxuser@% 14651USER@localhost maxtest@localhost maxtest@% 14693USER@localhost skysql@localhost skysql@% 14735USER@localhost cliuser@localhost cliuser@% repuser@localhost repuser@%
|
||||
MaxScale>
|
||||
User names: @localhost @localhost.localdomain 14567USER@localhost monuser@localhost monuser@% 14609USER@localhost maxuser@localhost maxuser@% 14651USER@localhost maxtest@localhost maxtest@% 14693USER@localhost skysql@localhost skysql@% 14735USER@localhost cliuser@localhost cliuser@% repuser@localhost repuser@%
|
||||
MaxScale>
|
||||
|
||||
```
|
||||
|
||||
@ -663,7 +663,7 @@ accepted.
|
||||
|
||||
```
|
||||
MaxScale> shutdown service RWSplit
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
## Restart A Stopped Service
|
||||
@ -689,14 +689,14 @@ configured within MariaDB MaxScale.
|
||||
MaxScale> list servers
|
||||
Servers.
|
||||
-------------------+-----------------+-------+-------------+--------------------
|
||||
Server | Address | Port | Connections | Status
|
||||
Server | Address | Port | Connections | Status
|
||||
-------------------+-----------------+-------+-------------+--------------------
|
||||
server1 | 127.0.0.1 | 3000 | 0 | Master, Running
|
||||
server2 | 127.0.0.1 | 3001 | 0 | Slave, Running
|
||||
server3 | 127.0.0.1 | 3002 | 0 | Slave, Running
|
||||
server4 | 127.0.0.1 | 3003 | 0 | Slave, Running
|
||||
-------------------+-----------------+-------+-------------+--------------------
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
## Server Details
|
||||
@ -714,12 +714,12 @@ Server 0x6501d0 (server2)
|
||||
Server Version: 10.1.22-MariaDB
|
||||
Node Id: 3001
|
||||
Master Id: 3000
|
||||
Slave Ids:
|
||||
Slave Ids:
|
||||
Repl Depth: 1
|
||||
Number of connections: 0
|
||||
Current no. of conns: 0
|
||||
Current no. of operations: 0
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
If the server has a non-zero value set for the server configuration item
|
||||
@ -796,7 +796,7 @@ Session | Client | Service | State
|
||||
11 | ::ffff:127.0.0.1 | RWSplit | Session ready for routing
|
||||
-----------------+-----------------+----------------+--------------------------
|
||||
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
This will give a list of client connections.
|
||||
@ -816,7 +816,7 @@ Session 11
|
||||
Connected: Thu Apr 20 09:51:31 2017
|
||||
|
||||
Idle: 82 seconds
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
# Descriptor Control Blocks
|
||||
@ -841,20 +841,20 @@ Descriptor Control Blocks
|
||||
------------------+----------------------------+--------------------+----------
|
||||
DCB | State | Service | Remote
|
||||
------------------+----------------------------+--------------------+----------
|
||||
0x68c0a0 | DCB for listening socket | RWSplit |
|
||||
0x6e23f0 | DCB for listening socket | CLI |
|
||||
0x691710 | DCB for listening socket | SchemaRouter |
|
||||
0x68c0a0 | DCB for listening socket | RWSplit |
|
||||
0x6e23f0 | DCB for listening socket | CLI |
|
||||
0x691710 | DCB for listening socket | SchemaRouter |
|
||||
0x7fffe40130f0 | DCB in the polling loop | CLI | localhost
|
||||
0x6b7540 | DCB for listening socket | RWSplit-Hint |
|
||||
0x6cd020 | DCB for listening socket | ReadConn |
|
||||
0x6b7540 | DCB for listening socket | RWSplit-Hint |
|
||||
0x6cd020 | DCB for listening socket | ReadConn |
|
||||
0x7fffd80130f0 | DCB in the polling loop | RWSplit | ::ffff:127.0.0.1
|
||||
0x7fffdc014590 | DCB in the polling loop | RWSplit |
|
||||
0x7fffdc0148d0 | DCB in the polling loop | RWSplit |
|
||||
0x7fffdc014c60 | DCB in the polling loop | RWSplit |
|
||||
0x7fffdc014ff0 | DCB in the polling loop | RWSplit |
|
||||
0x7fffdc014590 | DCB in the polling loop | RWSplit |
|
||||
0x7fffdc0148d0 | DCB in the polling loop | RWSplit |
|
||||
0x7fffdc014c60 | DCB in the polling loop | RWSplit |
|
||||
0x7fffdc014ff0 | DCB in the polling loop | RWSplit |
|
||||
------------------+----------------------------+--------------------+----------
|
||||
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
A MariaDB MaxScale server that has activity on it will however have many more
|
||||
@ -1027,7 +1027,7 @@ Monitor | Status
|
||||
---------------------+---------------------
|
||||
MySQL-Monitor | Running
|
||||
---------------------+---------------------
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
## Details Of A Particular Monitor
|
||||
@ -1056,7 +1056,7 @@ Slave configured: NO
|
||||
Slave IO running: NO
|
||||
Slave SQL running: NO
|
||||
Master ID: -1
|
||||
Master binlog file:
|
||||
Master binlog file:
|
||||
Master binlog position: 0
|
||||
|
||||
Server: server2
|
||||
@ -1090,7 +1090,7 @@ Master binlog file: binlog.000001
|
||||
Master binlog position: 435
|
||||
|
||||
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
## Shutting Down A Monitor
|
||||
@ -1107,7 +1107,7 @@ Monitor | Status
|
||||
---------------------+---------------------
|
||||
MySQL-Monitor | Stopped
|
||||
---------------------+---------------------
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
## Restarting A Monitor
|
||||
@ -1123,7 +1123,7 @@ Monitor | Status
|
||||
---------------------+---------------------
|
||||
MySQL-Monitor | Running
|
||||
---------------------+---------------------
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
# MaxScale Status Commands
|
||||
@ -1156,7 +1156,7 @@ Pending event queue length averages:
|
||||
1 | Polling | | | |
|
||||
2 | Processing | 1 | 0x6e0dd0 | <202400ms | IN|OUT
|
||||
3 | Polling | | | |
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
The resultant output returns data as to the average thread utilization for the
|
||||
@ -1176,7 +1176,7 @@ MaxScale> show tasks
|
||||
Name | Type | Frequency | Next Due
|
||||
--------------------------+----------+-----------+-------------------------
|
||||
Load Average | Repeated | 10 | Thu Apr 20 10:02:26 2017
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
# Administration Commands
|
||||
@ -1207,7 +1207,7 @@ readconnroute | Router | V1.1.0 | 2.0.0 | GA
|
||||
cli | Router | V1.0.0 | 2.0.0 | GA
|
||||
----------------+-----------------+---------+-------+-------------------------
|
||||
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
This command provides important version information for the module. Each module
|
||||
@ -1318,7 +1318,7 @@ command.
|
||||
|
||||
```
|
||||
MaxScale> shutdown maxscale
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
# Runtime Configuration Changes
|
||||
@ -1720,7 +1720,7 @@ No of poll completions with descriptors
|
||||
8 0
|
||||
9 0
|
||||
>= 10 0
|
||||
MaxScale>
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
If the "Number of DCBs with pending events" grows rapidly it is an indication
|
||||
@ -1750,38 +1750,38 @@ Average event queue length: 1
|
||||
| Number of events
|
||||
Duration | Queued | Executed
|
||||
---------------+------------+-----------
|
||||
< 100ms | 27 | 26
|
||||
100 - 200ms | 0 | 0
|
||||
200 - 300ms | 0 | 0
|
||||
300 - 400ms | 0 | 0
|
||||
400 - 500ms | 0 | 0
|
||||
500 - 600ms | 0 | 0
|
||||
600 - 700ms | 0 | 0
|
||||
700 - 800ms | 0 | 0
|
||||
800 - 900ms | 0 | 0
|
||||
900 - 1000ms | 0 | 0
|
||||
1000 - 1100ms | 0 | 0
|
||||
1100 - 1200ms | 0 | 0
|
||||
1200 - 1300ms | 0 | 0
|
||||
1300 - 1400ms | 0 | 0
|
||||
1400 - 1500ms | 0 | 0
|
||||
1500 - 1600ms | 0 | 0
|
||||
1600 - 1700ms | 0 | 0
|
||||
1700 - 1800ms | 0 | 0
|
||||
1800 - 1900ms | 0 | 0
|
||||
1900 - 2000ms | 0 | 0
|
||||
2000 - 2100ms | 0 | 0
|
||||
2100 - 2200ms | 0 | 0
|
||||
2200 - 2300ms | 0 | 0
|
||||
2300 - 2400ms | 0 | 0
|
||||
2400 - 2500ms | 0 | 0
|
||||
2500 - 2600ms | 0 | 0
|
||||
2600 - 2700ms | 0 | 0
|
||||
2700 - 2800ms | 0 | 0
|
||||
2800 - 2900ms | 0 | 0
|
||||
2900 - 3000ms | 0 | 0
|
||||
> 3000ms | 0 | 0
|
||||
MaxScale>
|
||||
< 100ms | 27 | 26
|
||||
100 - 200ms | 0 | 0
|
||||
200 - 300ms | 0 | 0
|
||||
300 - 400ms | 0 | 0
|
||||
400 - 500ms | 0 | 0
|
||||
500 - 600ms | 0 | 0
|
||||
600 - 700ms | 0 | 0
|
||||
700 - 800ms | 0 | 0
|
||||
800 - 900ms | 0 | 0
|
||||
900 - 1000ms | 0 | 0
|
||||
1000 - 1100ms | 0 | 0
|
||||
1100 - 1200ms | 0 | 0
|
||||
1200 - 1300ms | 0 | 0
|
||||
1300 - 1400ms | 0 | 0
|
||||
1400 - 1500ms | 0 | 0
|
||||
1500 - 1600ms | 0 | 0
|
||||
1600 - 1700ms | 0 | 0
|
||||
1700 - 1800ms | 0 | 0
|
||||
1800 - 1900ms | 0 | 0
|
||||
1900 - 2000ms | 0 | 0
|
||||
2000 - 2100ms | 0 | 0
|
||||
2100 - 2200ms | 0 | 0
|
||||
2200 - 2300ms | 0 | 0
|
||||
2300 - 2400ms | 0 | 0
|
||||
2400 - 2500ms | 0 | 0
|
||||
2500 - 2600ms | 0 | 0
|
||||
2600 - 2700ms | 0 | 0
|
||||
2700 - 2800ms | 0 | 0
|
||||
2800 - 2900ms | 0 | 0
|
||||
2900 - 3000ms | 0 | 0
|
||||
> 3000ms | 0 | 0
|
||||
MaxScale>
|
||||
```
|
||||
|
||||
The statics are defined in 100ms buckets, with the count of the events that fell
|
||||
|
||||
@ -25,7 +25,7 @@ passwd=mypwd
|
||||
|
||||
The module generates the list of databases based on the servers parameter using the connecting client's credentials. The user and passwd parameters define the credentials that are used to fetch the authentication data from the database servers. The credentials used only require the same grants as mentioned in the configuration documentation.
|
||||
|
||||
The list of databases is built by sending a SHOW DATABASES query to all the servers. This requires the user to have at least USAGE and SELECT grants on the databases that need be sharded.
|
||||
The list of databases is built by sending a SHOW DATABASES query to all the servers. This requires the user to have at least USAGE and SELECT grants on the databases that need be sharded.
|
||||
|
||||
If you are connecting directly to a database or have different users on some of the servers, you need to get the authentication data from all the servers. You can control this with the `auth_all_servers` parameter. With this parameter, MariaDB MaxScale forms a union of all the users and their grants from all the servers. By default, the schemarouter will fetch the authentication data from all servers.
|
||||
|
||||
|
||||
@ -130,7 +130,7 @@ servers=dbbubble1,dbbubble2,dbbubble3,dbbubble4,dbbubble5
|
||||
user=maxscale
|
||||
passwd=6628C50E07CCE1F0392EDEEB9D1203F3
|
||||
```
|
||||
The table you wish to store in Cassandra in called HighScore and will contain the same columns in both the MariaDB table and the Cassandra table. The first step is to install a MariaDB instance with the Cassandra storage engine to act as a bridge server between the relational database and Cassandra. In this bridge server add a table definition for the HighScore table with the engine type set to Cassandra.
|
||||
The table you wish to store in Cassandra in called HighScore and will contain the same columns in both the MariaDB table and the Cassandra table. The first step is to install a MariaDB instance with the Cassandra storage engine to act as a bridge server between the relational database and Cassandra. In this bridge server add a table definition for the HighScore table with the engine type set to Cassandra.
|
||||
See [Cassandra Storage Engine Overview]( https://mariadb.com/kb/en/mariadb/cassandra-storage-engine-overview/) for details.
|
||||
Add this server into the MariaDB MaxScale configuration and create a service that will connect to this server.
|
||||
```
|
||||
|
||||
@ -175,7 +175,7 @@ CLI | cli | 2 | 2
|
||||
% maxadmin list servers
|
||||
Servers.
|
||||
-------------------+-----------------+-------+-------------+--------------------
|
||||
Server | Address | Port | Connections | Status
|
||||
Server | Address | Port | Connections | Status
|
||||
-------------------+-----------------+-------+-------------+--------------------
|
||||
dbserv1 | 192.168.2.1 | 3306 | 0 | Running, Synced, Master
|
||||
dbserv2 | 192.168.2.2 | 3306 | 0 | Running, Synced, Slave
|
||||
|
||||
@ -30,7 +30,7 @@ enabled=1
|
||||
gpgcheck=0
|
||||
```
|
||||
|
||||
### Install the software
|
||||
### Install the software
|
||||
|
||||
```
|
||||
# yum install pacemaker corosync crmsh
|
||||
@ -74,7 +74,7 @@ For each node, add all the server names into `/etc/hosts`.
|
||||
|
||||
### Prepare authkey for optional cryptographic use
|
||||
|
||||
On one of the nodes, say node2 run the corosync-keygen utility and follow
|
||||
On one of the nodes, say node2 run the corosync-keygen utility and follow
|
||||
|
||||
```
|
||||
[root@node2 ~]# corosync-keygen
|
||||
@ -263,7 +263,7 @@ The Corosync / Pacemaker cluster is ready to be configured to manage resources.
|
||||
The MariaDB MaxScale init script in `/etc/init.d./maxscale` allows to start, stop, restart and monitor the MariaDB MaxScale process running on the system.
|
||||
|
||||
```
|
||||
[root@node1 ~]# /etc/init.d/maxscale
|
||||
[root@node1 ~]# /etc/init.d/maxscale
|
||||
Usage: /etc/init.d/maxscale {start|stop|status|restart|condrestart|reload}
|
||||
```
|
||||
|
||||
@ -389,7 +389,7 @@ Version: 1.1.10-14.el6_5.3-368c726
|
||||
|
||||
Online: [ node1 node2 node3 ]
|
||||
|
||||
MaxScale (lsb:maxscale): Started node1
|
||||
MaxScale (lsb:maxscale): Started node1
|
||||
```
|
||||
|
||||
### The resource cannot be migrated to node1 for a failure
|
||||
@ -422,7 +422,7 @@ Version: 1.1.10-14.el6_5.3-368c726
|
||||
|
||||
Online: [ node1 node2 node3 ]
|
||||
|
||||
MaxScale (lsb:maxscale): Started node2
|
||||
MaxScale (lsb:maxscale): Started node2
|
||||
|
||||
Failed actions:
|
||||
|
||||
@ -519,9 +519,9 @@ Online: [ node1 node2 node3 ]
|
||||
|
||||
Resource Group: maxscale_service
|
||||
|
||||
maxscale_vip (ocf::heartbeat:IPaddr2): Started node2
|
||||
maxscale_vip (ocf::heartbeat:IPaddr2): Started node2
|
||||
|
||||
MaxScale (lsb:maxscale): Started node2
|
||||
MaxScale (lsb:maxscale): Started node2
|
||||
```
|
||||
|
||||
With both resources on node2, now MariaDB MaxScale service will be reachable via the configured VIP address 192.168.122.125.
|
||||
|
||||
@ -27,11 +27,11 @@ If you already have a SSH key generated, you can skip this next step and go to t
|
||||
To generate a new set of SSH keys, we will use `ssh-keygen`.
|
||||
|
||||
```
|
||||
[root@localhost ~]# ssh-keygen
|
||||
[root@localhost ~]# ssh-keygen
|
||||
Generating public/private rsa key pair.
|
||||
Enter file in which to save the key (/root/.ssh/id_rsa):
|
||||
Enter passphrase (empty for no passphrase):
|
||||
Enter same passphrase again:
|
||||
Enter file in which to save the key (/root/.ssh/id_rsa):
|
||||
Enter passphrase (empty for no passphrase):
|
||||
Enter same passphrase again:
|
||||
Your identification has been saved in /root/.ssh/id_rsa.
|
||||
Your public key has been saved in /root/.ssh/id_rsa.pub.
|
||||
The key fingerprint is:
|
||||
@ -101,17 +101,17 @@ sync{
|
||||
default.rsyncssh,
|
||||
|
||||
-- This is where the maxscale.cnf file is copied from.
|
||||
source="/etc",
|
||||
source="/etc",
|
||||
|
||||
-- This is the user and host where the maxscale.cnf is copied to.
|
||||
-- Change this to the user and destination host where you want maxscale.cnf to be synchronized to.
|
||||
host="user@192.168.122.100",
|
||||
host="user@192.168.122.100",
|
||||
|
||||
-- This is where the maxscale.cnf is copied to on the remote host.
|
||||
targetdir="/etc",
|
||||
targetdir="/etc",
|
||||
|
||||
-- This is an optional section which defines a custom SSH port. Uncomment to enable.
|
||||
-- ssh={port=2222},
|
||||
-- ssh={port=2222},
|
||||
|
||||
-- These are values passed to rsync. Only change these if you know what you are doing.
|
||||
rsync={
|
||||
@ -139,9 +139,9 @@ settings{
|
||||
|
||||
sync{
|
||||
default.rsyncssh,
|
||||
source="/etc",
|
||||
host="maxuser@192.168.0.50",
|
||||
targetdir="/etc",
|
||||
source="/etc",
|
||||
host="maxuser@192.168.0.50",
|
||||
targetdir="/etc",
|
||||
rsync={
|
||||
compress=true,
|
||||
_extra = {[[--filter=+ *maxscale.cnf]],
|
||||
@ -153,9 +153,9 @@ rsync={
|
||||
|
||||
sync{
|
||||
default.rsyncssh,
|
||||
source="/etc",
|
||||
host="syncuser@192.168.122.105",
|
||||
targetdir="/etc",
|
||||
source="/etc",
|
||||
host="syncuser@192.168.122.105",
|
||||
targetdir="/etc",
|
||||
rsync={
|
||||
compress=true,
|
||||
_extra = {[[--filter=+ *maxscale.cnf]],
|
||||
|
||||
@ -16,7 +16,7 @@ Currently the user can connect to maxinfo from any remote IP and to localhost as
|
||||
type=service
|
||||
router=maxinfo
|
||||
user=monitor
|
||||
passwd=EBD2F49C3B375812A8CDEBA632ED8BBC
|
||||
passwd=EBD2F49C3B375812A8CDEBA632ED8BBC
|
||||
```
|
||||
|
||||
The listener section defines the protocol, port and other information needed to create a listener for the service. To listen on a port using the MySQL protocol a section as shown below should be added to the configuration file.
|
||||
@ -61,7 +61,7 @@ The maxinfo supports a small subset of SQL statements in addition to the MySQL s
|
||||
% mysqladmin -hmaxscale.mariadb.com -P9003 -umonitor -pxyz ping
|
||||
mysqld is alive
|
||||
% mysqladmin -hmaxscale.mariadb.com -P9003 -umonitor -pxyz status
|
||||
Uptime: 72 Threads: 1 Sessions: 11
|
||||
Uptime: 72 Threads: 1 Sessions: 11
|
||||
%
|
||||
```
|
||||
|
||||
@ -168,7 +168,7 @@ mysql> show status;
|
||||
+---------------------------+-------+
|
||||
22 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
mysql>
|
||||
```
|
||||
|
||||
## Show services
|
||||
@ -191,7 +191,7 @@ mysql> show services;
|
||||
+----------------+----------------+--------------+----------------+
|
||||
8 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
mysql>
|
||||
```
|
||||
|
||||
The show services command does not accept a like clause and will ignore any like clause that is given.
|
||||
@ -217,7 +217,7 @@ mysql> show listeners;
|
||||
+----------------+-----------------+-----------+------+---------+
|
||||
9 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
mysql>
|
||||
```
|
||||
|
||||
The show listeners command will ignore any like clause passed to it.
|
||||
@ -245,7 +245,7 @@ mysql> show sessions;
|
||||
+-----------+---------------+----------------+---------------------------+
|
||||
11 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
mysql>
|
||||
```
|
||||
|
||||
## Show clients
|
||||
@ -262,7 +262,7 @@ mysql> show clients;
|
||||
+-----------+---------------+---------+---------------------------+
|
||||
2 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
mysql>
|
||||
```
|
||||
|
||||
## Show servers
|
||||
@ -281,7 +281,7 @@ mysql> show servers;
|
||||
+---------+-----------+------+-------------+---------+
|
||||
4 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
mysql>
|
||||
```
|
||||
|
||||
## Show modules
|
||||
@ -306,7 +306,7 @@ mysql> show modules;
|
||||
+----------------+-------------+---------+-------------+----------------+
|
||||
10 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
mysql>
|
||||
```
|
||||
|
||||
## Show monitors
|
||||
@ -367,7 +367,7 @@ mysql> show eventTimes;
|
||||
+---------------+-------------------+---------------------+
|
||||
30 rows in set (0.02 sec)
|
||||
|
||||
mysql>
|
||||
mysql>
|
||||
```
|
||||
|
||||
Each row represents a time interval, in 100ms increments, with the counts representing the number of events that were in the event queue for the length of time that row represents and the number of events that were executing of the time indicated by the row.
|
||||
@ -422,7 +422,7 @@ $ curl http://maxscale.mariadb.com:8003/status
|
||||
{ "Variable_name" : "Max_event_queue_length", "Value" : 1},
|
||||
{ "Variable_name" : "Max_event_queue_time", "Value" : 0},
|
||||
{ "Variable_name" : "Max_event_execution_time", "Value" : 1}]
|
||||
$
|
||||
$
|
||||
```
|
||||
|
||||
## Services
|
||||
@ -496,7 +496,7 @@ $ curl http://maxscale.mariadb.com:8003/sessions
|
||||
{ "Session" : "0x1a5c0b0", "Client" : , "Service" : "Filter Service", "State" : "Listener Session"},
|
||||
{ "Session" : "0x1a5c530", "Client" : , "Service" : "Split Service", "State" : "Listener Session"},
|
||||
{ "Session" : "0x19ac1c0", "Client" : , "Service" : "Test Service", "State" : "Listener Session"}]
|
||||
$
|
||||
$
|
||||
```
|
||||
|
||||
## Clients
|
||||
|
||||
@ -109,7 +109,7 @@ The best way to describe this process is with an example.
|
||||
|
||||
User `'jdoe'@'192.168.0.200` has the following grant on the cluster:
|
||||
`GRANT SELECT, INSERT, UPDATE, DELETE ON *.* TO 'jdoe'@'192.168.0.200'`.
|
||||
When the user connects directly to the server it will see it as
|
||||
When the user connects directly to the server it will see it as
|
||||
`'jdoe'@'192.168.0.200` connecting to the server and it will match
|
||||
the grant for `'jdoe'@'192.168.0.200`.
|
||||
|
||||
|
||||
@ -207,7 +207,7 @@ CLI | cli | 2 | 2
|
||||
|
||||
Servers.
|
||||
-------------------+-----------------+-------+-------------+--------------------
|
||||
Server | Address | Port | Connections | Status
|
||||
Server | Address | Port | Connections | Status
|
||||
-------------------+-----------------+-------+-------------+--------------------
|
||||
dbserv1 | 192.168.2.1 | 3306 | 0 | Running, Slave
|
||||
dbserv2 | 192.168.2.2 | 3306 | 0 | Running, Master
|
||||
|
||||
@ -228,7 +228,7 @@ Servers.
|
||||
|
||||
-------------------+-----------------+-------+-------------+--------------------
|
||||
|
||||
Server | Address | Port | Connections | Status
|
||||
Server | Address | Port | Connections | Status
|
||||
|
||||
-------------------+-----------------+-------+-------------+--------------------
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ that can be run from a command line to check the status or a host or service.
|
||||
Nagios uses the results from plugins to determine the current status of hosts and
|
||||
services on your network.
|
||||
Nagios core executes a plugin whenever there is a need to check the status
|
||||
of a service or host.
|
||||
of a service or host.
|
||||
|
||||
While MariaDB MaxScale resources and status can be monitored via CLI using
|
||||
maxadmin commands, Nagios Plugin provides an automated way for system administration
|
||||
@ -31,7 +31,7 @@ details on respective resources.
|
||||
Current resources are: modules, services, listeners, servers, sessions, filters.
|
||||
|
||||
3. check_maxscale_monitor.pl: This command provides you status of the configured
|
||||
monitor modules on MariaDB MaxScale server.
|
||||
monitor modules on MariaDB MaxScale server.
|
||||
|
||||
In order to use these scripts on your Nagios Server, you need to copy them
|
||||
from the MariaDB MaxScale binary package or download them from source tree on GitHub.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
# Data archiving with Mqfilter and Tee filters
|
||||
|
||||
This tutorial gives a quick look into how you can combine various filters to create
|
||||
This tutorial gives a quick look into how you can combine various filters to create
|
||||
systems for archiving data for analysis. The aim of this tutorial is to show
|
||||
what can be done with MariaDB MaxScale's filters rather than demonstrate a proven method
|
||||
of archiving data. For this tutorial you will need two MariaDB/MySQL servers, one for
|
||||
@ -27,8 +27,8 @@ Since the archive server will not replicate from the main server, we don't need
|
||||
set up replication between the two. The only thing we need to do is to create the
|
||||
users we will use for monitoring and authentication.
|
||||
|
||||
The process of creating monitoring and authentication users for MariaDB MaxScale is described
|
||||
in the Creating Database Users section of the
|
||||
The process of creating monitoring and authentication users for MariaDB MaxScale is described
|
||||
in the Creating Database Users section of the
|
||||
[MariaDB MaxScale Tutorial](MaxScale-Tutorial.md#creating-database-users).
|
||||
|
||||
## Setting up RabbitMQ server
|
||||
@ -322,7 +322,7 @@ sudo maxadmin list servers
|
||||
|
||||
Servers.
|
||||
-------------------+-----------------+-------+-------------+--------------------
|
||||
Server | Address | Port | Connections | Status
|
||||
Server | Address | Port | Connections | Status
|
||||
-------------------+-----------------+-------+-------------+--------------------
|
||||
production-1 | 192.168.0.200 | 3306 | 0 | Running
|
||||
archive-1 | 192.168.0.201 | 3000 | 0 | Running
|
||||
|
||||
@ -11,7 +11,7 @@ MariaDB MaxScale will appear to the client as a database server with the combina
|
||||
This document is designed as a simple tutorial on schema-based sharding using MariaDB MaxScale in an environment in which you have two servers. The object of this tutorial is to have a system that, to the client side, acts like a single MySQL database but actually is sharded between the two servers.
|
||||
|
||||
The database users should be configured according to [the configuration guide](../Getting-Started/Configuration-Guide.md). The [MaxScale Tutorial](MaxScale-Tutorial.md) contains easy to follow instructions on how to set up MaxScale.
|
||||
|
||||
|
||||
This tutorial will assume the user is using of the binary distributions available and has installed this in the default location. The process of configuring MariaDB MaxScale will be covered within this document. The installation and configuration of the MySQL servers will not be covered in-depth.
|
||||
|
||||
## Preparing MaxScale
|
||||
|
||||
@ -37,7 +37,7 @@ filter(){
|
||||
# and we add the current date to the end of the 2 lines in the titleblock
|
||||
#date=$(date +"%B %e, %Y")
|
||||
printf -v date "%(%B %e, %Y)T"
|
||||
#awk ' /^$/ {p++} p==1{printf "%% %s\n", "'"$date"'";p++} !p{printf "%% "} {print} '
|
||||
#awk ' /^$/ {p++} p==1{printf "%% %s\n", "'"$date"'";p++} !p{printf "%% "} {print} '
|
||||
awk ' NR==1{ printf "%% " } # put % in front of first line
|
||||
NR==2{ printf " " } # put some space in front of 2nd line. pandoc requires this to continue the title
|
||||
NR==3{ printf "%% %s", "'"$date"'" } # 3rd line becomes the date.
|
||||
@ -49,10 +49,10 @@ filter(){
|
||||
|
||||
pandoc_vars=(
|
||||
-V fontsize=12pt
|
||||
-V version=1.10
|
||||
-V geometry:margin=1in
|
||||
-V version=1.10
|
||||
-V geometry:margin=1in
|
||||
--toc
|
||||
-t latex
|
||||
-t latex
|
||||
--latex-engine=xelatex
|
||||
--template="$template"
|
||||
)
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user