From c3a243cd30f50e1ff9a23144c9c03205e1ec4e8a Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Thu, 14 May 2015 15:32:57 +0300 Subject: [PATCH] Fixed typos. --- Documentation/Documentation-Contents.md | 6 ++++++ Documentation/monitors/Galera-Monitor.md | 4 ++-- Documentation/monitors/MM-Monitor.md | 4 ++-- Documentation/monitors/MySQL-Monitor.md | 4 ++-- Documentation/monitors/NDB-Cluster-Monitor.md | 4 ++-- 5 files changed, 14 insertions(+), 8 deletions(-) diff --git a/Documentation/Documentation-Contents.md b/Documentation/Documentation-Contents.md index 74969c7d1..47e2c77b2 100644 --- a/Documentation/Documentation-Contents.md +++ b/Documentation/Documentation-Contents.md @@ -53,6 +53,12 @@ Here are detailed documents about the filters MaxScale offers. They contain conf - [Database Firewall Filter](filters/Database-Firewall-Filter.md) - [RabbitMQ Filter](filters/RabbitMQ-Filter.md) +## Monitors + - [MySQL Monitor](monitors/MySQL-Monitor.md) + - [Galera Monitor](monitors/Galera-Monitor.md) + - [Multi-Master Monitor](monitors/MM-Monitor.md) + - [MySQL Cluster Monitor](monitors/NDB-Cluster-Monitor.md) + ## Utilities - [RabbitMQ Consumer Client](filters/RabbitMQ-Consumer-Client.md) diff --git a/Documentation/monitors/Galera-Monitor.md b/Documentation/monitors/Galera-Monitor.md index 8e1a403c9..ffe54fb83 100644 --- a/Documentation/monitors/Galera-Monitor.md +++ b/Documentation/monitors/Galera-Monitor.md @@ -24,7 +24,7 @@ Here are optional parameters that are common for all the monitors. ### `monitor_interval` -This is the time the monitor waits between each cycle of monitoring. The default value of 10000 milliseconds (10 seconds) should be lowered if you want a faster response to changes in the server states. The value is defined in milliseconds and the smallest possible value is 100 illiseconds. +This is the time the monitor waits between each cycle of monitoring. The default value of 10000 milliseconds (10 seconds) should be lowered if you want a faster response to changes in the server states. The value is defined in milliseconds and the smallest possible value is 100 milliseconds. ``` monitor_interval=2500 @@ -76,7 +76,7 @@ available_when_donor=true ### `disable_master_role_setting` -This disables the assingment of master and slave roles to the Galera cluster nodes. If this option is enabled, Synced is the only status assigned by this monitor. +This disables the assignment of master and slave roles to the Galera cluster nodes. If this option is enabled, Synced is the only status assigned by this monitor. ``` disable_master_role_setting=true diff --git a/Documentation/monitors/MM-Monitor.md b/Documentation/monitors/MM-Monitor.md index c9b4a852d..00375d4bf 100644 --- a/Documentation/monitors/MM-Monitor.md +++ b/Documentation/monitors/MM-Monitor.md @@ -2,7 +2,7 @@ ## Overview -The Multi-Master Monitor is a monitoring module for MaxScale that monitors Master-Master replicatio. It assigns master and slave roles inside MaxScale based on whether the read_only parameter on a server is set to off or on. +The Multi-Master Monitor is a monitoring module for MaxScale that monitors Master-Master replication. It assigns master and slave roles inside MaxScale based on whether the read_only parameter on a server is set to off or on. ## Configuration @@ -24,7 +24,7 @@ Here are optional parameters that are common for all the monitors. ### `monitor_interval` -This is the time the monitor waits between each cycle of monitoring. The default value of 10000 milliseconds (10 seconds) should be lowered if you want a faster response to changes in the server states. The value is defined in milliseconds and the smallest possible value is 100 illiseconds. +This is the time the monitor waits between each cycle of monitoring. The default value of 10000 milliseconds (10 seconds) should be lowered if you want a faster response to changes in the server states. The value is defined in milliseconds and the smallest possible value is 100 milliseconds. ``` monitor_interval=2500 diff --git a/Documentation/monitors/MySQL-Monitor.md b/Documentation/monitors/MySQL-Monitor.md index a3560c548..ab643109e 100644 --- a/Documentation/monitors/MySQL-Monitor.md +++ b/Documentation/monitors/MySQL-Monitor.md @@ -2,7 +2,7 @@ ## Overview -The MySQL Monitor is a monitoring module for MaxScale that monitors a Master-Slave replication cluster. It assigns master and slave roles inside MaxScale according to the acutal replication tree in the cluster. +The MySQL Monitor is a monitoring module for MaxScale that monitors a Master-Slave replication cluster. It assigns master and slave roles inside MaxScale according to the actual replication tree in the cluster. ## Configuration @@ -24,7 +24,7 @@ Here are optional parameters that are common for all the monitors. ### `monitor_interval` -This is the time the monitor waits between each cycle of monitoring. The default value of 10000 milliseconds (10 seconds) should be lowered if you want a faster response to changes in the server states. The value is defined in milliseconds and the smallest possible value is 100 illiseconds. +This is the time the monitor waits between each cycle of monitoring. The default value of 10000 milliseconds (10 seconds) should be lowered if you want a faster response to changes in the server states. The value is defined in milliseconds and the smallest possible value is 100 milliseconds. ``` monitor_interval=2500 diff --git a/Documentation/monitors/NDB-Cluster-Monitor.md b/Documentation/monitors/NDB-Cluster-Monitor.md index a2e608b7e..a9f453678 100644 --- a/Documentation/monitors/NDB-Cluster-Monitor.md +++ b/Documentation/monitors/NDB-Cluster-Monitor.md @@ -2,7 +2,7 @@ ## Overview -The MySQL Cluster Monitor is a monitoring module for MaxScale that monitors Master-Master replicatio. It assigns master and slave roles inside MaxScale based on whether the read_only parameter on a server is set to off or on. +The MySQL Cluster Monitor is a monitoring module for MaxScale that monitors a MySQL Cluster. It assigns a NDB status for the server if it is a part of a MySQL Cluster. ## Configuration @@ -24,7 +24,7 @@ Here are optional parameters that are common for all the monitors. ### `monitor_interval` -This is the time the monitor waits between each cycle of monitoring. The default value of 10000 milliseconds (10 seconds) should be lowered if you want a faster response to changes in the server states. The value is defined in milliseconds and the smallest possible value is 100 illiseconds. +This is the time the monitor waits between each cycle of monitoring. The default value of 10000 milliseconds (10 seconds) should be lowered if you want a faster response to changes in the server states. The value is defined in milliseconds and the smallest possible value is 100 milliseconds. ``` monitor_interval=2500