openstack/fuel-docs
Code Issues Proposed changes

Added MySQL/Pacemaker troubleshooting faq section

Browse Source
This commit is contained in:
Pavel Lechenko 2013-07-31 23:55:09 +04:00
parent c217b97bbc
commit 3c54f46340
4 changed files with 36 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
0060-frequently-asked-questions.rst
View File

@ -13,5 +13,6 @@ FAQ (Frequently Asked Questions)
.. include:: /pages/frequently-asked-questions/0070-common-technical-issues.rst
.. include:: /pages/frequently-asked-questions/0010-rabbitmq.rst
.. include:: /pages/frequently-asked-questions/0020-galera.rst
.. include:: /pages/frequently-asked-questions/0030-mysql-pacemaker.rst
.. include:: /pages/frequently-asked-questions/0080-other-questions.rst

5
pages/about-fuel/0030-how-it-works.rst
View File

@ -23,9 +23,14 @@ In practice, that means that the process of using Fuel looks like 1-2-3:
enabling you to maintain your cluster and adapt to your own configuration as
necessary.
.. rst-class:: centered
.. fancybox:: /_images/010-how-it-works_svg.png
:width: 300px
:height: 300px
:class: align-center
.. rst-class:: floater
Fuel comes with several pre-defined deployment configurations, some of which
include additional options from which you can choose.

16
pages/about-fuel/0040-reference-topologies.rst
View File

@ -12,14 +12,14 @@ its constituent components are tailored to one or more common cloud use cases.
Fuel provides the ability to create the following cluster types without requiring
extensive customization:
.. index:: Deployment Configurations, Single node
.. index:: Deployment Configurations; Single node
**Single node**: Perfect for getting a feel for how OpenStack works, the
Single-node installation is the simplest way to get OpenStack up and running.
The Single-node installation provides an easy way to install an entire OpenStack
cluster on a single physical server system or in a virtual machine environment.
.. index:: Deployment Configurations, Multi-node (non-HA)
.. index:: Deployment Configurations; Multi-node (non-HA)
**Multi-node (non-HA)**: The Multi-node (non-HA) installation enables you to try
out additional OpenStack services like Cinder, Neutron (formerly Quantum), and
@ -27,18 +27,18 @@ Swift without requiring the degree of increased hardware involved in ensuring
high availability. In addition to the ability to independently specify which
services to activate, you also have the following options:
.. index:: Deployment Configurations, Compact Swift non-HA
.. index:: Deployment Configurations; Compact Swift non-HA
**Compact Swift**: When you choose this option, Swift will be installed on
your controllers, reducing your hardware requirements by eliminating the need
for additional Swift servers.
.. index:: Deployment Configurations, Standalone Swift non-HA
.. index:: Deployment Configurations; Standalone Swift non-HA
**Standalone Swift**: This option enables you to install independant Swift
nodes, so that you can separate their operation from your controller nodes.
.. index:: Deployment Configurations, Multi-node (HA)
.. index:: Deployment Configurations; Multi-node (HA)
**Multi-node (HA)**: When you're ready to begin your move to production, the
Multi-node (HA) configuration is a straightforward way to create an OpenStack
@ -46,19 +46,19 @@ cluster that provides high availability. With three controller nodes and the
ability to individually specify services such as Cinder, Neutron, and Swift,
Fuel provides the following variations of the Multi-node (HA) configuration:
.. index:: Deployment Configurations, Compact Swift HA
.. index:: Deployment Configurations; Compact Swift HA
**Compact Swift**: When you choose this option, Swift will be installed on
your controllers, reducing your hardware requirements by eliminating the need
for additional Swift servers while still addressing high availability
requirements.
.. index:: Deployment Configurations, Standalone Swift HA
.. index:: Deployment Configurations; Standalone Swift HA
**Standalone Swift**: This option enables you to install independant Swift
nodes, so that you can separate their operation from your controller nodes.
.. index:: Deployment Configurations, Compact Neutron HA
.. index:: Deployment Configurations; Compact Neutron HA
**Compact Neutron**: If you don't need the flexibility of a separate Neutron
node, Fuel provides the option to combine your Neutron node with one of your

22
pages/frequently-asked-questions/0030-mysql-pacemaker.rst Normal file
View File

@ -0,0 +1,22 @@
Corosync crashes without network
--------------------------------
TOTEM, the network protocol used by Corosync exceeds its timeout. Corosync
sometimes crashes when networking is unavailable for a length of time.
Additionally, MySQL has stopped working.
**Workaround:**
#. Verify that corosync is really broken ``service corosync status``.
* You should see next error: ``corosync dead but pid file exists``
#. Start corosync manually ``service corosync start``.
#. Run ``ps -ef | grep mysql`` and kill ALL(!) **mysqld** and **mysqld_safe** processes.
#. Wait while pacemaker starts mysql processes again.
* You can check it with ``ps -ef | grep mysql`` command.
* If it doesn't start, run ``crm resource p_mysql`` start.
#. Check with ``crm status`` command that this host is part of the cluster and p_mysql is not within "Failed actions".