Remove trailing whitespace from documentation
Removed trailing whitespace from all documents.
This commit is contained in:
Markus Mäkelä
@ -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
|
||||
|
||||
Reference in New Issue
Block a user