From 2aaa65d0ae17ced8164c409b4585f49f8ed4902a Mon Sep 17 00:00:00 2001 From: Maria Zlatkova Date: Tue, 7 Jul 2015 18:44:17 +0300 Subject: [PATCH] [Monitoring Guide] Fix wrong command end Fixes wrong command end in MySQL section. Also adds few edits. Change-Id: I2a0e585d99d179d823bf541eecc922df59f49336 Closes-Bug: #1471270 --- .../monitoring-activities-details/mysql.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/pages/monitoring-guide/monitoring-activities-details/mysql.rst b/pages/monitoring-guide/monitoring-activities-details/mysql.rst index 1d904476c..cf520671c 100644 --- a/pages/monitoring-guide/monitoring-activities-details/mysql.rst +++ b/pages/monitoring-guide/monitoring-activities-details/mysql.rst @@ -4,7 +4,7 @@ MySQL ----- The MySQL database running on the OpenStack controller nodes is a -central component, because it is used by almost all the OpenStack +central component because it is used by almost all the OpenStack components as their primary data persistence storage. Therefore, it is critical to monitor the healthiness of this component on each of the controller nodes in the cluster. @@ -109,7 +109,7 @@ verified using the command:: These poll SQL metrics can be collected using the following SQL command:: - SHOW GLOBAL STATUS WHERE Variable_name= + SHOW GLOBAL STATUS WHERE Variable_name=; See MySQL `server status variables`_ for details. @@ -127,10 +127,10 @@ See MySQL `server status variables`_ for details. | **Metrics related to the MySQL cluster** The high availability of the MySQL database is supported in -active/passive mode with one master and several slaves nodes. +active/passive mode with one master and several slave nodes. To ensure that the MySQL cluster remains highly available, you should -continuously monitor that slaves are ready to take over in case of a -master node failure. +continuously monitor that slave nodes are ready to take over in case +of a master node failure. .. list-table:: :header-rows: 1