No subject

"some important caveats apply: whilst exchanges and bindings survive the
loss of individual nodes, queues and their messages do not. This is because
a queue and its contents reside on exactly one node, thus the loss of a
node will render its queues unavailable."

--047d7b603bb047b94004cf8262d4
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 27, 2012 at 1:03 PM, David Buckingham <span dir=3D"ltr">&lt;<a =
href=3D"mailto:David.Buckingham at cbeyond.net" target=3D"_blank">David.Buckin=
gham at cbeyond.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div c=
lass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><p clas=
s=3D"">I=92m not quite sure where I may have gone wrong.=A0 By adding the n=
ew clustered node as an upstream on rabbit1, I guess that I expected the sa=
me configuration would be pushed-to/created-on rabbit3 that was previously =
created on rabbit2.</p>
</div></blockquote><div><br></div><div>From the documentation on Highly Ava=
ilable Queues (<a href=3D"http://www.rabbitmq.com/ha.html">http://www.rabbi=
tmq.com/ha.html</a>) regarding using a cluster:</div><div><br></div><div>
&quot;some important caveats apply: whilst exchanges and bindings survive t=
he loss of individual nodes, queues and their messages do not. This is beca=
use a queue and its contents reside on exactly one node, thus the loss of a=
 node will render its queues unavailable.&quot;=A0</div>
</div></div>

--047d7b603bb047b94004cf8262d4--