summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMatthew Sackman <matthew@rabbitmq.com>2011-06-21 14:14:14 +0100
committerMatthew Sackman <matthew@rabbitmq.com>2011-06-21 14:14:14 +0100
commit9e6aa4f7e8057565c8ecea2b8de68bafd5850064 (patch)
treef3ed408d9d0843c9fad747e4675f84931eb994c3 /docs
parent34a62af5202cb8682c7833baa1cd2a0e266b4e9c (diff)
downloadrabbitmq-server-git-9e6aa4f7e8057565c8ecea2b8de68bafd5850064.tar.gz
Rip out support for dynamically adding or removing queue mirrors
Diffstat (limited to 'docs')
-rw-r--r--docs/rabbitmqctl.1.xml43
1 files changed, 0 insertions, 43 deletions
diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml
index cc3d4d2a51..a0f031927f 100644
--- a/docs/rabbitmqctl.1.xml
+++ b/docs/rabbitmqctl.1.xml
@@ -1361,49 +1361,6 @@
</variablelist>
</refsect2>
-
- <refsect2>
- <title>Mirrored Queue Management</title>
- <para>
- Mirrored queues can have slaves dynamically added, and slaves
- or the master dynamically dropped. Refer to the <ulink
- url="http://www.rabbitmq.com/ha.html">High Availability
- guide</ulink> for further details about mirrored queues in
- general.
- </para>
-
- <variablelist>
- <varlistentry>
- <term><cmdsynopsis><command>add_queue_mirror</command> <arg choice="req"><replaceable>queue_name</replaceable></arg> <arg choice="req"><replaceable>node</replaceable></arg></cmdsynopsis></term>
- <listitem>
- <para>
- Attempts to add a mirror of the queue
- <command>queue_name</command> on
- <command>node</command>. This will only succeed if the
- queue was declared a mirrored queue and if there is no
- mirror of the queue already on the node. If it succeeds,
- the new mirror will start off as an empty slave.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><cmdsynopsis><command>drop_queue_mirror</command> <arg choice="req"><replaceable>queue_name</replaceable></arg> <arg choice="req"><replaceable>node</replaceable></arg></cmdsynopsis></term>
- <listitem>
- <para>
- Attempts to drop a mirror of the queue
- <command>queue_name</command> on
- <command>node</command>. This will only succeed if the
- queue was declared a mirrored queue and if there is a
- mirror of the queue already on the node. If the node
- contains the master of the queue, a slave on some other
- node will be promoted to become the new master. It is
- not permitted to drop the only node of a mirrored-queue.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </refsect2>
</refsect1>
</refentry>