Fix 4 typos

in Configuring the controller for high availability
on OpenStack High Availability Guide
Closes-Bug: #1476442

Change-Id: Ia70506c612255e392c09c16a2408bcea97ef38ad
This commit is contained in:
Atsushi SAKAI 2015-07-21 21:22:02 +09:00
parent d4602948d3
commit 91335a20e2
3 changed files with 4 additions and 4 deletions

View File

@ -67,7 +67,7 @@ Galera/MySQL in:
.. note ::
The galara package is now called galera-3 and is already a dependency
The galera package is now called galera-3 and is already a dependency
of mariadb-galera-server. Therefore it should not be specified on the
command line.
@ -258,7 +258,7 @@ to recover from an error:
| wsrep_flow_control_sent | 0 |
| wsrep_flow_control_recv | 0 |
| wsrep_cert_deps_distance | 1.029703 |
|riaDB with Galera (Red Hat-based platforms) wsrep_apply_oooe | 0.024752 |
| wsrep_apply_oooe | 0.024752 |
| wsrep_apply_oool | 0.000000 |
| wsrep_apply_window | 1.024752 |
| wsrep_commit_oooe | 0.000000 |

View File

@ -385,7 +385,7 @@ Note the following:
This logic is repeated until the number of online nodes
in the cluster reaches 2.
In order to allow the cluster to step down from 2 members to only 1,
the ``auto_tie_breaker`` paramaeter needs to be set;
the ``auto_tie_breaker`` parameter needs to be set;
this is not recommended for production environments.
- ``last_man_standing_window`` specifies the time, in milliseconds,

View File

@ -96,7 +96,7 @@ the availability of service since it is resilient to failures.
Production servers should run (at least) three RabbitMQ servers;
for testing and demonstration purposes,
it is possible to run only two servers.
In this section, we congfigure two nodes,
In this section, we configure two nodes,
called `rabbit1` and `rabbit2`.
To build a broker, we need to ensure
that all nodes have the same Erlang cookie file.